Skip to main content
Glama

middleware_get_capabilities

Read-only

Middleware admin only: read enabled provider accounts, capabilities and transaction input schemas. Use this before middleware_submit_transaction. Requires the static MCP/REST admin bearer token. Provider operations and credentials remain in the existing middleware service. For linked tenants, pass the public customer_id (cus_…) on all middleware admin calls.

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

Input Schema

NameRequiredDescriptionDefault
account_idNo
customer_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / customer_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Customer Id"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: it requires the static MCP/REST admin bearer token, notes provider credentials stay in the middleware service, and explains tenant scoping via the public customer_id for linked tenants.

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?

Four sentences, front-loaded with audience and purpose, then prerequisite, then tenant scoping. Dense but every sentence adds operational information; the middleware-internals sentence is the least load-bearing.

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?

An output schema exists, so return values need not be described, and the description covers the auth requirement, the sequencing relative to submit_transaction, and tenant scoping. The only remaining gap is what account_id selects, which matters for a two-parameter tool at 0% schema coverage.

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 0%, so the description must carry parameter meaning. It explains customer_id well (public cus_… identifier, required on linked-tenant admin calls) but says nothing about account_id, leaving the agent to infer it is a provider account identifier from the capability listing.

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?

Specific verb and resource: 'read enabled provider accounts, capabilities and transaction input schemas.' It also names the audience ('Middleware admin only') and positions itself relative to the sibling middleware_submit_transaction, so an agent can tell it apart from the other middleware_* and generic get_* tools.

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?

Explicit sequencing guidance: 'Use this before middleware_submit_transaction' tells the agent when this tool is the right call. There is no explicit when-not guidance or mention of what to do if the caller is not an admin, but the precondition and ordering are clear.

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.