Skip to main content
Glama

Title and description budget

bpj_page_meta_budget
Read-onlyIdempotent

Measure visible characters in a page title and description against your editorial 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": {
      "title": "<title>",
      "description": "<description>",
      "titleLimit": "<titleLimit>",
      "descriptionLimit": "<descriptionLimit>"
    },
    "name": "bpj_page_meta_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
titleLimitYes
descriptionYes
descriptionLimitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered and the bar is lower. The description adds the meaningful nuance that only 'visible' characters count, but it does not clarify what visibility means (markup, entities, emoji) or what the result reports when limits are breached.

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 no filler. It is efficient, though given zero schema coverage the terseness trades away information an agent needs.

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?

With four required parameters at 0% coverage and no output schema, the description should explain the counting rule and what is returned (counts, remaining budget, pass/fail). It does neither, leaving an agent to guess at the semantics of the core measurement.

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%, so the description must carry the burden for four required parameters. It maps loosely onto title, description, and the two limits, but says nothing about how 'visible characters' are counted, whether the limit is inclusive, or how titleLimit and descriptionLimit are applied. The distinction between the two limit parameters is left entirely to the schema's titles.

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: measuring visible characters in a page title and description against editorial limits. It is clear what the tool does and no sibling name overlaps this measurement role. It stops short of explicitly differentiating itself from adjacent budget tools such as bpj_page_transfer_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?

The phrase 'your editorial limits' implies the caller supplies thresholds, but there is no statement of when to reach for this tool versus alternatives, no prerequisites, and no note about what to do when a limit is exceeded. Usage is only inferable from the tool's purpose, not from guidance.

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.