Skip to main content
Glama

Compute an NMEA sentence checksum

bpj_nmea_sentence_checksum
Read-onlyIdempotent

XOR the ASCII payload bytes and assemble a checksummed NMEA sentence.

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": {
      "value": "<value>"
    },
    "name": "bpj_nmea_sentence_checksum"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds some behavioral context by explaining that it XORs payload bytes and assembles a full NMEA sentence, but it does not clarify the expected input form or what exactly is returned.

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?

The description is a single efficient sentence with the core operation front-loaded. It is not padded or repetitive, though it is too terse to resolve the input-format ambiguity.

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?

For a one-parameter tool with no output schema, the description should clarify both the expected input syntax and whether the return value is a checksum or a full assembled sentence. It leaves both points ambiguous, which is a meaningful gap for an agent invoking the tool.

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 input schema only says the value is a string up to 240 characters. The description implies the value is the ASCII payload to be XORed, but it does not clarify whether the input should include NMEA framing such as '$' or '*', nor what byte range is expected.

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 operation: XOR ASCII payload bytes and assemble a checksummed NMEA sentence. This is more precise than the name alone, though it does not differentiate the tool from other checksum siblings such as bpj_isin_checksum or bpj_adler32.

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 guidance on when to use this tool versus other checksum or sentence-related tools. It does not state prerequisites, input format expectations, or exclusions.

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.