Skip to main content
Glama

recovery.identity.get_scope

recovery.identity.get_scope
Read-onlyIdempotent

Return the clinic's canonical inclusions, exclusions and minimum age as factual policy. Does not decide safety or patient suitability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recovery.identity.get_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
resultYes
statusYes
urgencyYes
versionYes
warningsYes
confidenceYes
provenanceYes
limitationsYes
scope_matchYes
missing_dataYes
allowed_actionsYes
clinical_decisionYes
safety_gate_statusYes
requires_clinician_reviewYes
autonomous_clearance_issuedYes
autonomous_clinical_clearanceYes
individualized_prescription_issuedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly, idempotent and non-destructive, so the description earns credit for the one thing annotations can't express: the scope boundary that this returns policy facts rather than clinical judgments. It adds no detail on freshness or source of the policy, which would have completed the picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the returned content front-loaded and the scope exclusion second. Every clause carries information; nothing is repeated from the name or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't explain return structure, and with no parameters and full annotation coverage the only remaining gap is how the clinic is resolved in context. The definition is otherwise complete for a trivial read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters means there is nothing to disambiguate, so the baseline applies. The description correctly says nothing about inputs, matching the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (return) and enumerates the exact resource contents (inclusions, exclusions, minimum age) as factual policy. It is immediately distinguishable from sibling decision tools because it explicitly frames the output as policy data, not a judgment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line 'Does not decide safety or patient suitability' implicitly routes the agent to recovery.clinical_decision.safety_screen or patient_fit when a decision is needed, which is useful context. It stops short of naming those siblings explicitly, so an agent must infer the alternative rather than being handed it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources