Skip to main content
Glama

MedaRep

Practice profile

practice_profile
Read-onlyIdempotent

A PECOS group practice by PAC ID: size, employment model and who decides, Medicare cases by family with its top surgeons, device payments by company, and sites.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pac_id": "<pac_id>"
    },
    "name": "practice_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pac_idYesPECOS PAC ID; from search, rank_territory or surgeon_profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is fully covered structurally. The description adds real value by disclosing what comes back (the section-by-section payload), which matters because there is no output schema, but it says nothing about permissions, rate limits, or what happens when a PAC ID is not found.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; each comma-separated clause names a distinct payload section. Dense but readable, and nothing is redundant — the only mild cost is that the sections are listed without explaining how they are grouped or ordered.

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?

For a one-parameter, read-only lookup with no output schema, the description supplies the most important missing piece: the shape of the returned content. Remaining gaps (error/empty behavior, how the top surgeons list is ranked or limited) are minor for this complexity level.

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

Parameters3/5

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

There is one parameter at 100% schema coverage, and the schema already defines pac_id as a PECOS PAC ID with its upstream sources. The description only echoes the keying by PAC ID, adding no format, validation, or sourcing detail beyond the schema.

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

Purpose4/5

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

Names the resource (a PECOS group practice) and its key (PAC ID), and enumerates the payload categories — size, employment model and decision-makers, Medicare cases by family with top surgeons, device payments by company, and sites. That distinguishes it from surgeon_profile and company_profile even without naming them explicitly, though the phrase is a noun label rather than a verb.

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

Usage Guidelines3/5

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

Usage is only implied: the reader infers this is the profile lookup to use when holding a PAC ID. There is no explicit when-to-use versus surgeon_profile/company_profile/facility_profile, and no stated prerequisites or failure behavior for an unknown ID; the schema carries the provenance hint (from search, rank_territory or surgeon_profile).

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