Skip to main content
Glama
backworkai
by backworkai

list_jurisdictions

Find the Medicare Administrative Contractor jurisdiction for a patient's state by retrieving MAC names, jurisdiction codes, and covered states.

Instructions

Get list of Medicare Administrative Contractor (MAC) jurisdictions. Returns MAC names, jurisdiction codes, and covered states. Use this to find the right jurisdiction for a patient's state.

Example:

  • list_jurisdictions() - get all MAC jurisdictions and their states

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches the list of MAC jurisdictions from the Verity API endpoint '/jurisdictions' and formats them into a readable text output including jurisdiction codes, MAC names, states, types, and websites.
    async () => {
      try {
        const result = await verityRequest<any>("/jurisdictions");
    
        const lines: string[] = [`MAC Jurisdictions (${result.data.length} total):\n`];
    
        result.data.forEach((jur: any) => {
          lines.push(`[${jur.jurisdiction_code}] ${jur.jurisdiction_name || ""}`);
          lines.push(`  MAC: ${jur.mac_name}${jur.mac_code ? ` (${jur.mac_code})` : ""}`);
          if (jur.states?.length) lines.push(`  States: ${jur.states.join(", ")}`);
          if (jur.mac_type) lines.push(`  Type: ${jur.mac_type}`);
          if (jur.website_url) lines.push(`  Website: ${jur.website_url}`);
          lines.push("");
        });
    
        return {
          content: [{ type: "text", text: lines.join("\n") }],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error listing jurisdictions: ${error instanceof Error ? error.message : String(error)}` }],
        };
      }
    }
  • src/index.ts:615-650 (registration)
    Registration of the 'list_jurisdictions' tool with the MCP server, including description, empty input schema (no parameters), and reference to the handler function.
    server.registerTool(
      "list_jurisdictions",
      {
        description: `Get list of Medicare Administrative Contractor (MAC) jurisdictions.
    Returns MAC names, jurisdiction codes, and covered states.
    Use this to find the right jurisdiction for a patient's state.
    
    Example:
    - list_jurisdictions() - get all MAC jurisdictions and their states`,
        inputSchema: {},
      },
      async () => {
        try {
          const result = await verityRequest<any>("/jurisdictions");
    
          const lines: string[] = [`MAC Jurisdictions (${result.data.length} total):\n`];
    
          result.data.forEach((jur: any) => {
            lines.push(`[${jur.jurisdiction_code}] ${jur.jurisdiction_name || ""}`);
            lines.push(`  MAC: ${jur.mac_name}${jur.mac_code ? ` (${jur.mac_code})` : ""}`);
            if (jur.states?.length) lines.push(`  States: ${jur.states.join(", ")}`);
            if (jur.mac_type) lines.push(`  Type: ${jur.mac_type}`);
            if (jur.website_url) lines.push(`  Website: ${jur.website_url}`);
            lines.push("");
          });
    
          return {
            content: [{ type: "text", text: lines.join("\n") }],
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error listing jurisdictions: ${error instanceof Error ? error.message : String(error)}` }],
          };
        }
      }
    );
  • Tool schema defining the description and input schema (empty, as the tool takes no parameters).
      {
        description: `Get list of Medicare Administrative Contractor (MAC) jurisdictions.
    Returns MAC names, jurisdiction codes, and covered states.
    Use this to find the right jurisdiction for a patient's state.
    
    Example:
    - list_jurisdictions() - get all MAC jurisdictions and their states`,
        inputSchema: {},
      },
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the return data (MAC names, codes, states) and includes an example, but lacks details on behavioral traits such as rate limits, error handling, or data freshness. The description adds some value but doesn't fully compensate for the absence of annotations.

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?

The description is appropriately sized and front-loaded: it starts with the core purpose, then details the output, usage guidance, and an example. Every sentence adds value without redundancy, making it efficient and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough for a read-only lookup tool. It explains what it does, what it returns, and how to use it, though it could benefit from more behavioral context like response format or limitations.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, a baseline of 4 is appropriate as it doesn't need to compensate for any gaps.

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 clearly states the specific action ('Get list'), resource ('Medicare Administrative Contractor (MAC) jurisdictions'), and output details ('MAC names, jurisdiction codes, and covered states'). It distinguishes itself from sibling tools like 'check_prior_auth' or 'get_policy' by focusing on jurisdiction lookup rather than policy or authorization operations.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: 'Use this to find the right jurisdiction for a patient's state.' This provides clear context for application, though it doesn't specify when not to use it or name alternatives among siblings, but the guidance is sufficient for a 5 given the explicit purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/backworkai/verity_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server