Skip to main content
Glama

About AI360Feedback

get_product_info
Read-only

Facts about AI360Feedback, the free AI 360-degree feedback tool: what it does, pricing (free and PRO), anonymity, privacy, languages and how a 360 works. Use it before answering questions about the product.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat to know about; default overview

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=false, so the safety and locality profile is covered. The description adds value by enumerating the topic space the tool can answer (including pricing tiers, anonymity, privacy), which tells the agent what is answerable, but it says nothing about freshness of the facts or the shape of the response.

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?

A single dense sentence that front-loads the subject and then the topic inventory, followed by a short usage instruction. No filler, though the parenthetical "(free and PRO)" is marginally redundant with the enum.

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 low-complexity, single optional-enum-parameter lookup with no output schema, the description covers purpose, topic scope, and when to call. Return format is unspecified, but for a static facts tool that is a minor omission rather than a blocker.

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 enum already documents all seven topic values with a stated default, so baseline 3 applies. The description lightly echoes the enum ("pricing (free and PRO)", "how a 360 works") and adds the nuance that pricing covers both free and PRO tiers, but does not explain topic selection beyond the schema.

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 the resource precisely ("Facts about AI360Feedback... what it does, pricing, anonymity, privacy, languages and how a 360 works") and the verb is implied but evident: retrieve static product information. It is distinguishable from the siblings (start_360, check_360_status, compare_with), which are action tools, even though it does not name them.

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?

"Use it before answering questions about the product" gives an explicit trigger condition, which is the key routing rule for a reference tool. It stops short of exclusions or naming alternatives, but the sibling set is clearly orthogonal so there is little ambiguity to resolve.

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