Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

twins_search

Read-onlyIdempotent

Public digital twins whose name, city or description contains the words (all of them when q is...

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / kind / description
      Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • removedInput schema / properties / mode / description
      Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  2. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • addedInput schema / properties / mode / description
      Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  3. Changed2 schema fields changed
    • removedInput schema / properties / kind / description
      Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • removedInput schema / properties / mode / description
      Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  4. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • addedInput schema / properties / mode / description
      Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  5. Changed2 schema fields changed
    • removedInput schema / properties / kind / description
      Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • removedInput schema / properties / mode / description
      Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  6. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • addedInput schema / properties / mode / description
      Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  7. Changed2 schema fields changed
    • removedInput schema / properties / kind / description
      Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • removedInput schema / properties / mode / description
      Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  8. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • addedInput schema / properties / mode / description
      Added value: +"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
  9. Changed3 schema fields changed
    • removedInput schema / properties / kind / properties
      Removed value: -null
    • removedInput schema / properties / mode / properties
      Removed value: -null
    • removedInput schema / properties / q / properties
      Removed value: -null
  10. Changed5 schema fields changed
    • removedInput schema / properties / kind / description
      Removed value: -"only this kind: printfarm, factory, warehouse, truck, airport, port, city, robot, sim"
    • addedInput schema / properties / kind / properties
      Added value: +null
    • removedInput schema / properties / mode / description
      Removed value: -"only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed"
    • addedInput schema / properties / mode / properties
      Added value: +null
    • addedInput schema / properties / q / properties
      Added value: +null
  11. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "only twins whose numbers are this: observed (live feed), recorded (real data replayed), simulated, mixed",
+  "enum": [
+    "observed",
+    "recorded",
+    "simulated",
+    "mixed",
+    "undeclared"
+  ],
+  "type": "string"
+}
  12. First observed

TDQS

C2.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful scope by specifying that only public twins are searched and which fields are matched, but it omits result format and pagination details.

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 brief, but it is an incomplete fragment that ends mid-thought ('when q is...'), so its brevity reflects truncation and under-specification rather than disciplined conciseness.

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 three-parameter search tool with no output schema, the description is incomplete. It leaves licensing/mode filtering and result behavior unexplained, and the truncation prevents an agent from knowing the full matching rule.

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 description must carry parameter meaning. It partially explains q by saying it matches words across name, city, or description, but kind and mode are completely unaddressed, leaving two of three parameters undocumented.

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

Purpose3/5

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

The description identifies the resource (public digital twins) and the search fields (name, city, description), so the broad purpose is inferable. However, it is a sentence fragment with no explicit verb such as 'search', and it does not differentiate itself from siblings like twins_near or twin_get.

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 twins_near, twins_community, or twin_get. The text implies text-based search but provides no exclusions, prerequisites, or alternative-selection advice.

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

All ce-net 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