Skip to main content
Glama

Read monitoring limits and receipt

get_monitoring
Read-onlyIdempotent

Read a monitoring permission: expiry, ceilings, settled charges and anything still pending. A pending maximum is not a final charge.

Permission: monitoring:manage.

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": {
      "monitoring_id": "<monitoring_id>"
    },
    "name": "get_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitoring_idYesThe monitoring ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond the annotations by noting that a pending maximum is not a final charge and by specifying the required permission scope.

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 short, front-loaded, and wastes no words. Each sentence contributes either scope, a critical semantic caveat, or auth requirements.

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?

Given the low complexity, rich annotations, fully documented single parameter, and existence of an output schema, the description contains everything an agent needs to call this tool correctly. It covers purpose, authorization, and the key caveat about pending charges.

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 description coverage is 100%, and the single parameter is fully documented in the schema. The description does not add any further meaning about the monitoring_id parameter beyond what the schema already provides.

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 states a specific verb and resource ('Read a monitoring permission') and enumerates the fields returned: expiry, ceilings, settled charges, and pending items. This clearly distinguishes it from sibling operations such as quote_monitoring, approve_monitoring, and revoke_monitoring.

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?

The description implies reading an existing monitoring permission and states the required permission scope, but it does not explicitly say when to use this tool versus alternatives like quote_monitoring or approve_monitoring. The usage context is adequate but not fully directive.

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