Skip to main content
Glama
Sign In

Quartermaster eSIM

by io.github.dvirmimon123-tech
OverviewDiscussionsAdmin

Read store policies

get_policies
Read-only

Read the store's rules as machine-readable JSON before you spend. Use it to learn refund and dispute terms, mandate and registration caps, supplier trust and the quote lifetime. Returns every policy (mandate, refund, dispute, supplier trust, registration), the store terms and the product and agent JSON Schemas. Read-only and free; it takes only agent_id and principal_id (no agent_key) and nothing is charged.

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": "get_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoYour agent id (or X-Agent-Id header)
agent_keyNoSecret returned by register_agent (or X-Agent-Key header)
principal_idNoThe principal you act for (or X-Principal-Id header)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / agent_id / pattern
      Added value: +"^[A-Za-z0-9._:-]{3,128}$"
    • addedInput schema / properties / agent_key / maxLength
      Added value: +256
    • addedInput schema / properties / principal_id / pattern
      Added value: +"^[A-Za-z0-9._:@-]{3,128}$"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing cost ('free', 'nothing is charged') and authentication requirements ('takes only agent_id and principal_id (no agent_key)'). It also previews the return payload, so an agent knows what it will get and what it will not be billed.

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?

Front-loaded with purpose and timing, then payload, then cost/auth notes in a sensible order. There is mild redundancy between the second sentence's enumeration and the third sentence's parenthetical policy list, but no filler.

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 carries the burden and does it: it lists the returned policy categories, the store terms, and the embedded JSON Schemas, plus cost and credential requirements. Nothing essential to deciding whether and how to call it is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real information the schema does not: that agent_key is unnecessary despite being defined in the schema, narrowing the practical parameter set to two. It gives no format guidance for agent_id or principal_id, which the schema already covers.

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?

Names a specific verb and resource ('Read the store's rules as machine-readable JSON') and states its scope: refund/dispute terms, mandate and registration caps, supplier trust, quote lifetime, and the bundled JSON Schemas. The phrase 'before you spend' places it relative to purchase-oriented siblings without ambiguity.

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 a clear when-to-use condition ('before you spend') and enumerates the decisions the output informs. It does not explicitly name or exclude an alternative sibling, so it falls just short of a full when/when-not routing statement.

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

All Quartermaster eSIM toolsInspect
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