Skip to main content
Glama

Robots meta reader

bpj_robots_meta_reader
Read-onlyIdempotent

Interpret sitewide robots meta directives for indexing, link following and snippet limits.

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": {
      "directives": "<directives>"
    },
    "name": "bpj_robots_meta_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
directivesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful scope word "sitewide" and the three interpreted facets, but says nothing about how malformed or unknown directives are handled or in what form findings come back.

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?

One front-loaded sentence with no filler; the resource is stated before the facets. It is efficient, though its brevity is the reason the usage and parameter details are absent rather than a sign of careful trimming.

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?

With no output schema the description must hint at the return values, and listing indexing, link following and snippet limits does that in part. It still leaves unclear whether the result is parsed flags, a normalized directive list, or a list of issues, which matters for a tool whose whole job is interpretation.

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%, but the single property carries a self-explanatory title, "Robots content (comma-separated)", plus a 900-character cap, so format is partially conveyed by structured data. The description itself adds no semantics about accepted token values, case sensitivity, or separator handling, so it does not compensate for the coverage gap beyond restating the concept.

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 ("Interpret") and resource ("sitewide robots meta directives"), then names the exact facets covered: indexing, link following and snippet limits. That is enough for an agent to recognize it as a parser for robots meta content, though it does not distinguish itself from adjacent siblings such as bpj_cache_control_reader or bpj_page_meta_budget.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use framing, no prerequisites, and no mention of what this tool is not for. The agent must infer from the name alone that this consumes raw robots meta strings rather than fetching pages or reading HTTP headers.

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.