Skip to main content
Glama

Robots snippet limits

bpj_robots_snippet_directives
Read-onlyIdempotent

Build a robots meta tag from text, video and image preview limits, accepting -1 for unlimited length.

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": {
      "snippet": "<snippet>",
      "video": "<video>",
      "image": "<image>"
    },
    "name": "bpj_robots_snippet_directives"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes
videoYes
snippetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and not open-world, so the agent knows the safety profile. The description adds that -1 means unlimited length, but it does not describe the returned tag format, validation behavior, or how image categories are handled.

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?

The definition is a single front-loaded sentence with no filler. Every clause contributes to purpose or parameter meaning.

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?

For a simple three-parameter, read-only builder with no output schema, the description covers the core construction task and the key -1 sentinel. It could be more complete by stating the output format and image allowed values, but the annotations and schema titles fill most of the remaining gaps.

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 the semantic load. It maps the three inputs to text, video, and image preview limits and explains the important -1 sentinel for the numeric limits, but it does not clarify the image string's allowed values or units/limits beyond what the schema titles and constraints already show.

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 verb and resource: build a robots meta tag from text, video, and image preview limits. This is clear enough to distinguish it from unrelated? No, from a reader/parser sibling, though it does not explicitly name or contrast with bpj_robots_meta_reader.

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?

The description explains what the tool produces but gives no when-to-use guidance, prerequisites, or comparison to alternatives such as reading an existing robots meta tag. The intended use is only implied by the verb 'Build'.

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.