Skip to main content
Glama
Sign In

centric-demo

by io.github.centricai
OverviewDiscussionsAdmin

demo_temperature_check

Walk through the temperature check interaction for a demo contact: shows the prompt and the Positive / Neutral / Concern options, and returns a canned acknowledgment. Demonstrates the loop without saving anything.

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": {
      "contact": "<contact>"
    },
    "name": "demo_temperature_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNoOptional: the read to simulate. Omit to just see the prompt.
contactYesContact id or name, e.g. 'Isabella Chen'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the key traits: it shows the prompt and Positive/Neutral/Concern options, returns a canned acknowledgment, and does not save anything. That covers the non-persistent, simulation-only nature of the tool, though it does not discuss possible errors or contact lookup 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?

The description is two sentences, front-loaded with the interaction purpose and followed by the key behavioral detail that nothing is saved. Every phrase earns its place and there is no redundant repetition.

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 simple two-parameter demo tool with no output schema and no annotations, the description is largely complete. It explains what is shown, what is returned, and that nothing is persisted. Minor gaps include not clarifying whether the contact must already exist in the demo list or what happens on invalid input.

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 both parameters and the enum values. The description reinforces the Positive/Neutral/Concern options and the demo-contact context, but it adds little beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 interaction and resource: walking through the temperature check for a demo contact. It also clarifies that the tool shows prompt/options, returns a canned acknowledgment, and does not save, making its demo purpose clear. It does not explicitly distinguish itself from sibling tools, but there is no direct sibling equivalent among the listed tools.

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?

The description gives clear context for use: it is for a demo contact and demonstrates the loop without saving anything. This implies it is for demo/testing scenarios rather than real persistence. It does not name alternatives or explicitly state when not to use it, but the demo scope is evident.

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

All centric-demo 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