Zhiyong AI Technology Decision Radar

Compare public KG entities

compare_knowledge_entities

Read-only

Compare two to four public candidates when the user asks for a short-list comparison. Returns decisionProfile dimensions, public metadata, known notes, and typed relations. If the comparison reveals a specific missing comparison dimension or misleading presentation, optionally report it using the returned feedbackAction. This is never required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Two to four public entity ids, slugs, or exact names returned by search_knowledge_graph.
`language`	No	Optional output language override. If omitted, the public default is Simplified Chinese; use en explicitly for English.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`policy`	No
`entities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026
- removedOutput schema / properties / interactionContract
```
Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
```
Changed1 schema field changedSep 9, 2026
- addedOutput schema / properties / interactionContract
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / language / description

Previous value: -"Optional output language override. If omitted, the server uses Accept-Language and then Cloudflare IP country; the final fallback is English."New value: +"Optional output language override. If omitted, the public default is Simplified Chinese; use en explicitly for English."

First observedSep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description's enumeration of returned content is largely redundant with the existing output schema, and it adds only one genuinely new behavioral note: that reporting a missing dimension via feedbackAction is optional and "never required." No auth, rate-limit, or cost context is given.

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?

Three sentences, front-loaded with the trigger and scope before the return summary and the optional-feedback caveat. The final "This is never required." is mildly redundant with the preceding "optionally," but overall the text is tight.

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?

With an output schema present, the description need not explain return values, and annotations cover safety; what remains (when to invoke, entity-count bound, optional feedback path) is supplied. The one soft spot is the absent pointer to the single-entity sibling for non-comparative lookups.

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% — the ids format (ids/slugs/exact names from search_knowledge_graph, min 2/max 4) and the language enum with its Simplified-Chinese default are documented in the schema. The description adds no parameter-level meaning beyond that, so baseline 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?

States a concrete verb+resource (compare two to four public KG candidates) with explicit scope limits, which naturally distinguishes it from the single-entity sibling get_knowledge_entity. However, no sibling is named, so the differentiation is inferable rather than explicit.

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?

"when the user asks for a short-list comparison" gives a clear contextual trigger, and the 2–4 entity bound tells the agent when the tool is applicable. It stops short of naming alternatives (e.g. get_knowledge_entity for a single entity) or stating when not to use it.

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

All Zhiyong AI Technology Decision Radar tools Inspect

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

Need Help?