Skip to main content
Glama

Compare with another 360 tool

compare_with
Read-only

Compare AI360Feedback with another 360 feedback tool (e.g. Lattice, Culture Amp, 15Five, Spidergap, Effy, SurveyMonkey): pricing, free option, contract, AI. Returns a table and a link.

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": {
      "tool": "<tool>"
    },
    "name": "compare_with"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesName of the other tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description is consistent with it. The description adds value beyond the annotations by disclosing the return shape ("a table and a link") and the four comparison dimensions, though it says nothing about whether the compared data is cached or how current it is.

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?

One sentence, front-loaded with the verb and resource, followed by the dimensions covered and the return format. Every clause earns its place and nothing is 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 one-parameter, read-only comparison tool the description covers everything needed: the subject, the competitor space with examples, the comparison dimensions, and the output shape. No output schema exists, and the description compensates by naming the return format.

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 parameter already carries a description ("Name of the other tool"), so the baseline is 3. The description's list of concrete vendor names (Lattice, Culture Amp, 15Five, Spidergap, Effy, SurveyMonkey) does hint at the expected value format, but it is framed as comparison examples rather than as parameter guidance.

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 specific verb and resource ("Compare AI360Feedback with another 360 feedback tool") and enumerates the comparison axes: pricing, free option, contract, AI. That is far more concrete than a restated title. It does not explicitly differentiate itself from the nearby get_product_info sibling, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The implied trigger — a user weighing AI360Feedback against a competitor — is easy to infer from the phrasing and the named vendor examples. However, there is no explicit when-to-use/when-not guidance and no pointer to an alternative tool (e.g. get_product_info for details on AI360Feedback itself).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources