Skip to main content
Glama

MCP OAuth client-interop conformance

MCP OAuth conformance check

conformance_check
Read-only

run one full client x IdP-shape conformance matrix (the POST /check operation; x402 $0.01 per check unless your account has an active Solo subscription/trial, metered exactly as REST)

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

Input Schema

NameRequiredDescriptionDefault
clientsNo
idp_shapeNo
apply_shimsNo
full_matrixNo
server_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and destructiveHint=false; the description adds genuinely useful behavior the annotations don't carry: this is a paid POST operation at x402 $0.01 per check with a subscription/trial waiver and REST-equivalent metering. It stops short of disclosing runtime, what the matrix executes, or what the response contains. The readOnlyHint is not contradicted, since a check does not mutate stored data, though the charge is worth noting.

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?

A single front-loaded sentence with the action first and cost/metering in a parenthetical, with no filler. It is dense with jargon ('IdP-shape', 'x402', 'metered exactly as REST') that an unfamiliar agent may not parse, but nothing is wasted.

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?

For a five-parameter tool with a nested object, an enum, no output schema, and minimal annotations, the description should explain the matrix dimensions and what each knob does. It covers cost and the underlying endpoint but leaves the caller unable to confidently construct a request or anticipate results.

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% across all five parameters, so the description must compensate — and it explains none of them. Clients, idp_shape, apply_shims, full_matrix, and especially the nested server_config object are left entirely opaque, including how apply_shims or full_matrix interact with the 'full matrix' claim in the description.

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

Purpose4/5

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

The description states a specific action and resource: running one full client x IdP-shape conformance matrix, and frames it as 'the POST /check operation'. This is distinguishable from the billing/history siblings (claim_trial, subscribe_solo, subscription_status, run_history), though it never names those siblings or what a conformance matrix actually validates.

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?

Usage is only implied — an agent can infer you call this to run a conformance check, and the pricing clause hints you should have a Solo subscription/trial first. There is no explicit when-to-use vs. run_history, and no when-not guidance such as prerequisites for setting up clients or server_config before a check.

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