Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

caesar_cipher

Shift letters by any amount to encrypt, or reverse the shift to decrypt, keeping case and punctuation. Pure CPU, instant.

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": "caesar_cipher"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to shift
shiftNoShift amount (default 3)
decodeNoReverse the shift

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / decode
      Added value: +{
+  "description": "Reverse the shift",
+  "type": "boolean"
+}
    • addedInput schema / properties / shift
      Added value: +{
+  "description": "Shift amount (default 3)",
+  "type": "integer"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Text to shift",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "text"
+]
  4. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose some behavior: case and punctuation are preserved, it's pure CPU and instant, so no side effects or latency concerns. It omits how non-letter characters like digits or non-ASCII text are handled, and gives no warning that this is a toy cipher unsuitable for real encryption.

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 covering the operation, the reverse path, and the preservation guarantee, with a short performance note appended. Tight and readable, though the 'Pure CPU, instant' clause is somewhat filler for a trivially cheap operation.

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 three-parameter, no-output-schema utility with full schema coverage, the description covers the core operation and its key guarantee (case/punctuation preservation). Only minor gaps remain: handling of non-letter characters and the exact return shape.

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 100%, so the schema already documents text, shift (default 3), and decode. The description reinforces that shift can be 'any amount' and decode 'reverses the shift', but adds no syntax, range, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Shift letters') plus the bidirectional capability (encrypt/decrypt), so the agent knows exactly what the tool does. It doesn't explicitly distinguish itself from close siblings like rot13, atbash, or vigenere, though 'by any amount' implicitly separates it from the fixed-shift rot13.

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

Usage Guidelines3/5

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

Usage is implied by 'to encrypt, or reverse the shift to decrypt', giving the agent a rough sense of when to call it. There is no explicit guidance on choosing this over rot13 (fixed 13) or vigenere (keyword-based), and no statement of exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources