MCP tools reference
How your AI uses SpecMCP tools to answer certification and specification questions.
SpecMCP is one hosted MCP server. Your AI client discovers its tools after you connect to https://mcp.specmcp.com/mcp; you normally describe the outcome you need, and the assistant chooses the calls. The strongest results come from giving it the product or provider context and asking it to show its scope.
Describe the goal, not the tool call
Ask for the certification scope, implementation checklist, or release impact you need. SpecMCP’s tools are designed for your AI to compose into the right workflow.
Choose the right workflow
| Your question | Start with | Why |
|---|---|---|
| “What do we need to certify?” | list_scopes | Certification obligations are defined by a scope (Steckbrief). |
| “Which requirements apply to this feature?” | list_specs | First identify the specifications that govern the feature. |
| “What does A_22793-01 mean?” | get_requirement | A known ID can be retrieved directly. |
| “What changed in this release?” | get_spec_version_history | It supplies the exact version names for a comparison. |
Certification-scope tools
list_scopes
Lists the available certification programs and their current versions. Optionally filter by gemProdT (product type) or gemAnbT (provider type). Use it before asking which certification scope applies.
Returns: each scope’s slug, name, type, description, current version, and available versions.
List the certification scopes that could apply to our TI-Messenger client. Explain the candidates before selecting one.list_scope_specs
Takes a scope_slug from list_scopes and returns the exact specification versions that scope covers. Use this when you need the scope’s source context, rather than an exhaustive certification checklist.
After listing the candidates, use the selected scope’s slug to list its covered specs and explain which are relevant to service operations.list_scope_requirements
Takes a scope_slug and returns the complete set of requirements gematik actively verifies for that scope. Results include requirement ID, title, severity, source spec, verification type, and verification group. Optional filters: verification_group and table (ptv, atv, or both).
Use this for certification planning. It is the authoritative scope checklist; requirements in a referenced spec that are absent from this output are not certification gates for that scope.
For the selected scope, get the complete checklist. Group it by verification type and highlight every must or must_not requirement.diff_scope_versions
Compares two versions of one certification scope. It requires scope_slug and from_version; to_version defaults to the latest. Set include_content: true when you need the full text of changed requirements for a migration assessment.
Compare the previous and latest versions of this certification scope. Show added, removed, and modified requirements, with full text for the modified ones.Specification and requirement tools
list_specs
Lists the available specifications by category, including what each spec governs, who it applies to, key topics, current version, and any known draft versions. There are no inputs.
Use it to establish a defensible search boundary before requirement search.
List the current specs relevant to authentication in a TI-Messenger client. State which specs you will search and why.search_requirements
Performs semantic search within explicitly supplied spec_ids. It requires a query and the spec IDs from list_specs; optional controls are limit, severity, and include_drafts.
Returns: ranked matches with ID, title, severity, source spec/version, and similarity, but not the full requirement text. Follow with get_requirement or get_requirements for the requirements you need to interpret.
Prop
Type
Search the scoped specs for authentication requirements. Restrict results to must and must_not, then retrieve the full detail for the ten most relevant matches.get_requirement
Fetches the full detail of one requirement. Supply either the UUID returned by search or a gematik requirement_id, such as A_22793-01 or GS-A_4657. You can also pin a known ID to a specific version.
By default, a repeated ID resolves to the in-force version. Explicitly request a draft version only when you are assessing an upcoming change; draft results are marked non-binding.
get_requirements
Retrieves full detail for a batch of requirement IDs. Use it after search when several results need review together. Supply requirement_ids; optionally provide version to retrieve a particular version.
Retrieve the full details for these requirement IDs and turn them into an implementation checklist. Keep their IDs, severity, source spec, and cross-references.list_requirements
Returns all requirements for one spec_id, rather than the best semantic matches. Use it when completeness matters for a particular spec. You may filter by severity and choose a specific version.
This can produce a large result. Ask for a digest or a severity filter first unless you truly need the full list.
Version tools
get_spec_version_history
Lists the known versions and release information for one spec_id. Use it before a version comparison and to discover exact draft version names.
diff_versions
Compares two versions of one spec. Supply spec_id; if omitted, from_version defaults to the previous version and to_version to the current version. It distinguishes added, removed, and modified requirements, including gematik's revised -NN requirement IDs. Set include_content: true for full changed text.
Show the version history for gemSpec_TI-Messenger-Client, then compare the current version with the previous one. Include full content for mandatory changes and propose migration tasks.Reliable prompts
- Name the product, provider, feature, and known scope or spec.
- Ask the assistant to state which scopes and specs it searched, and which it excluded.
- Ask it to separate binding current requirements from drafts.
- For a certification decision, prefer the scope checklist over a broad semantic search.
- Keep requirement IDs and source specs in every ticket, checklist, or review note the assistant produces.