Skip to main content
Glama

Writing system profile

bpj_unicode_script_profile
Read-onlyIdempotent

Count characters from common Unicode scripts, with remaining characters grouped separately.

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": {
      "text": "<text>"
    },
    "name": "bpj_unicode_script_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuine behavioral fact beyond that: characters outside the common scripts are not dropped but grouped into a separate bucket. It does not say which scripts are covered, whether counts are returned as a mapping, or how the 'remaining' group is labeled.

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 sentence with no filler, and the core operation is front-loaded before the fallback-grouping caveat. It is efficient, though its brevity contributes to the underspecification noted elsewhere rather than being a virtue in itself.

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?

There is no output schema, so the description must carry the burden of explaining the return shape, yet it never says that results are per-script counts, which scripts are enumerated, or how unmapped characters are represented. For a profiling tool that produces a multi-bucket result, 'common scripts' and 'grouped separately' leave the agent guessing at the actual output.

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 single 'text' property has no inline documentation and its 6000-character limit is invisible to a reading of the description. However, with only one obvious input parameter named 'text', the description's reference to counting characters in a text implicitly covers it, so the gap is small rather than critical.

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 concrete verb (count) and resource (characters per Unicode script), so the agent can tell it produces a script-frequency profile. It stops short of naming or distinguishing itself from sibling profiling tools such as bpj_unicode_category_profile or bpj_unicode_scalar_inventory, and 'common Unicode scripts' is left undefined.

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 explicit when-to-use statement, no prerequisites, and no exclusions or alternatives. The agent can only infer from 'count characters from common Unicode scripts' that this is for analyzing the script composition of a text; nothing tells it when another profiler would be the better choice.

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.