Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Ping the INKEEDecoder server

inkeedecoder_ping
Read-onlyIdempotent

Checks that the server is running and returns the INKEEDecoder base URL it will use, without sending requests to the site. Use it to confirm configuration before calling lookup tools.

Instructions

Check that the server is running and report which INKEEDecoder base URL it will read from. Sends no request to the site. Use it to verify configuration before calling lookup tools.

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

Input Schema

NameRequiredDescriptionDefault
messageNoOptional message to echo back. Omit for a bare 'pong'.

Output Schema

NameRequiredDescriptionDefault
okYesAlways true — the server answered.
replyYesThe echo response.
serverYes
baseUrlYesBase URL that the lookup tools will read from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real value: no request is sent to the external site, and the response discloses the configured base URL. This is exactly the context an agent needs before trusting later calls; minor gap is no mention of failure/timeout behavior.

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

Conciseness5/5

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

Two short sentences, front-loaded with what the tool does, then the when-to-use guidance and the network-safety note. Nothing is redundant or padded.

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

Completeness5/5

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

For a health-check tool with an output schema covering the return payload and full annotation coverage, the description supplies everything needed: purpose, side-effect profile, and invocation timing. No missing information affects correct invocation.

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 coverage is 100% and the single optional 'message' parameter is documented in the schema itself with its echo/bare-pong behavior. The description adds no parameter information beyond that, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource: checks server liveness and reports the INKEEDecoder base URL in use. The 'Sends no request to the site' clause further distinguishes it from the lookup/search siblings, so an agent can tell what it does without opening the schema.

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

Usage Guidelines4/5

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

Explicitly says 'Use it to verify configuration before calling lookup tools,' which gives a clear when-to-use condition and implicitly rules out using it to fetch brand/ingredient data. No explicit when-not or named alternative tool, but the positioning is unambiguous.

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