Skip to main content
Glama

run_service_pack

Read-only

Run a commercial pack: insurance.corridor | govtech.emergency | govtech.mobility.

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": {
      "pack_id": "<pack_id>"
    },
    "name": "run_service_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
originNo
api_keyNo
pack_idYes
profileNosafest
locationNo
destinationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it doesn't say whether an api_key is required, what 'profile' defaults/values mean, or what 'safest' implies. For a tool with six parameters and an open-world execution verb ('Run'), the near-silence on behavior is a real gap.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but its brevity is under-specification rather than efficiency. There is no second sentence to explain what happens when the pack runs or how the parameters relate to it.

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

Completeness2/5

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

With six parameters, zero schema descriptions, and an output schema present (so return values need no explanation), the description should be carrying most of the weight and it isn't. The input contract an agent needs is largely missing; only pack_id is documented.

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

Parameters2/5

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

Schema description coverage is 0%, so the description is the only source of parameter meaning and it covers just one parameter, pack_id, by listing its three values. Origin, destination, location, api_key, and profile go entirely unexplained — a critical omission given things like profile's 'safest' default. The pack_id enumeration is the only added value.

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

Purpose3/5

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

The description gives a verb ('Run') and names the resource ('commercial pack') and enumerates three valid pack ids, which is useful. However, 'commercial pack' is unexplained jargon and the sentence never says what running a pack actually produces or does, so an agent still cannot picture the outcome. Sibling list_service_packs suggests this executes one of those packs, but the definition never makes that connection.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — nothing distinguishing this from list_service_packs, assess_journey_risk, or optimize_route. No prerequisites are stated, and the reader must guess whether pack_id values are the only accepted inputs.

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.