Skip to main content
Glama

Check agents.json

bursia_check_agents_json
Read-onlyIdempotent

Check one agent-readiness item on a public website: Directorio de agentes (agents.json) (/.well-known/agents.json or /.well-known/agent-directory.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_agents_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only, free' largely restates structured data. The genuinely additive part is the disclosure of which URLs are fetched (/.well-known/agents.json, /.well-known/agent-directory.json), but nothing is said about behavior when the file is absent or malformed.

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 resource and paths stated before the trailing read-only/pricing note. The 'Directorio de agentes' label is slightly redundant with the path list but costs little.

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?

For a one-parameter check tool with rich annotations this is close to sufficient, but with no output schema the description never indicates what a result looks like (found/not-found, parsed content, status detail). An agent knows what it probes but not what it gets back.

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?

Only one parameter with 100% schema description coverage ('Domain or https URL'), so the schema carries the burden. The description's path list hints at what the URL is used for but adds no format, normalization or scheme-handling rules beyond the schema.

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?

States a specific verb ('Check') plus the exact resource ('agents.json') and names the two well-known paths probed. That path detail cleanly separates it from siblings like bursia_check_agent_card, bursia_check_llms_txt and bursia_check_mcp_discovery without opening any schema.

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 on a public website' implies the usage context (single-item probe against a public domain), but it never names an alternative or exclusion — e.g. bursia_agent_readiness for a full audit or bursia_compare_readiness for comparison. The agent must infer the routing from sibling names alone.

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