Skip to main content
Glama

Check OpenAPI

bursia_check_openapi
Read-onlyIdempotent

Check one agent-readiness item on a public website: OpenAPI (/openapi.json or /.well-known/openapi.json). Read-only, free.

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": {
      "url": "<url>"
    },
    "name": "bursia_check_openapi"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by naming the two fallback paths probed and noting the call is free, so the agent knows both locations are checked in one invocation.

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?

A single sentence plus a short qualifier phrase; zero waste. The scope and the probed paths are front-loaded ahead of the cost note.

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

Completeness3/5

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

No output schema exists, and the description says nothing about what a result looks like — found vs. not found, status code, or whether partial matches count. For a one-parameter probe tool this is a modest but real gap an agent would want closed.

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?

Only one parameter and schema coverage is 100%, with the schema already saying "Domain or https URL". The description's "public website" adds a real constraint — the target must be publicly reachable — which the schema does not state.

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?

States a specific verb (check) and a precisely scoped resource: the OpenAPI document at /openapi.json or /.well-known/openapi.json on a public website. The exact probe paths make it unambiguous against siblings like bursia_check_agent_card or bursia_check_llms_txt, though it never explicitly contrasts itself with them.

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?

"Check one agent-readiness item" implies this is a single-check tool, which hints at the difference from the umbrella bursia_agent_readiness, but the relationship is left implicit. No statement of when to prefer this over the aggregate tool or what to do with a negative result.

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