Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_jce

Decode data using JCE by supplying the input and mode, returning the decoded output.

Instructions

[data] JCE

Parameters:

  • data (string): Data

  • mode (string): Mode

Outputs:

  • decoded (json): Decoded

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tool_jce"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoData
modeNoMode
decodedNoDecoded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it discloses nothing. It does not mention encryption/decryption, side effects, authentication, or output handling. The tool is a black box.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified. It lists parameters and outputs in a structured format, but the content is so sparse that it fails to communicate the tool's purpose or usage. It is not concise in a useful way; it is simply incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool appears to be a crypto-related operation (JCE), but with no annotations, no output schema, and unexplained parameters, the description is severely incomplete. An agent cannot infer how to invoke the tool correctly or interpret results.

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?

Although schema_description_coverage is 100%, the parameter descriptions in both the schema and the tool description are trivial labels (Data, Mode, Decoded) with no explanation of their meaning or accepted values. The description adds no value beyond the schema and leaves the agent guessing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lacks a verb and any explanation of what JCE does. It only repeats the tool name and lists parameters, offering no actionable purpose. It is essentially a tautology, providing no distinction from sibling crypto tools.

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

Usage Guidelines1/5

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

There is zero guidance on when to use this tool vs alternatives. No context, prerequisites, or exclusions. An agent would have no idea why this tool exists or when it should be selected.

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

Deploy Server

Other Tools