itemnumbers MBS schedule

Search MBS items

search_mbs_items

Read-onlyIdempotent

Find Medicare Benefits Schedule (MBS) items by item number or by words describing the procedure or service. Returns each match's descriptor, schedule fee and Medicare benefits from the current schedule. Use it first when you have a procedure but not an item number. Never put patient identifiers in the query.

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": {
      "query": "<query>"
    },
    "name": "search_mbs_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many items to return, 1 to 20. Default 10.
`query`	Yes	An item number or its start (for example 3038), or a few words naming the procedure or service (for example gallbladder removal). Never include patient names, dates of birth or other identifying details.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds useful behavioral context by naming the returned fields, noting the current schedule, and warning against patient identifiers; it does not discuss pagination or no-match behavior.

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?

Three tightly written sentences, front-loaded with what the tool does, followed by return content and the key usage/privacy constraint. No sentence is wasted.

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

Completeness5/5

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

With no output schema, the description appropriately names the returned fields. Annotations cover safety, and the schema covers parameters, so the description supplies enough context for an agent to call this search tool correctly.

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?

Schema coverage is 100%, so the input schema already documents both query and limit. The description reinforces the query modes and privacy constraint, but adds little beyond the schema and does not explain the limit parameter.

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?

States a specific verb and resource: finds MBS items by item number or descriptive words. The use case 'when you have a procedure but not an item number' helps separate it from exact-item lookup siblings, though it does not name those siblings explicitly.

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?

Gives clear when-to-use guidance: use it first when you know the procedure but not the item number. It does not name alternative tools or state when not to use it, so it stops short of full routing guidance.

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

All itemnumbers MBS schedule tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?