Skip to main content
Glama

Echoo public catalog

Read Echoo product facts

get_echoo_product_facts
Read-onlyIdempotent

Read current requirements, context tools and introductory credits from the public product catalog.

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_echoo_product_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
memoryYes
categoryYes
sourceUrlYes
descriptionYes
freeCreditsYes
minimumMacOSYes
screenContextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and determinism are covered by structured fields. The description contributes that the source is the public catalog (no auth or account context implied) and which facts come back, but adds nothing about freshness, caching, or size of the payload — modest value beyond the annotations.

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?

A single short sentence with no filler, front-loading the verb and the resource before the content list. Every clause carries information; nothing is redundant or padded.

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 zero parameters and an output schema present, the description need not explain invocation or return shape, and it correctly stays brief. The only shortfall is the absence of any positioning relative to the other catalog-reading siblings, which an agent would need in order to choose correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. Nothing in the description conflicts with the empty schema, and the enumerated returned categories loosely map to the properties an agent will see.

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 pairs a specific verb ("Read") with a scoped resource ("public product catalog") and enumerates the content categories returned: requirements, context tools, and introductory credits. That is clear enough for an agent to know what it yields, but it never distinguishes itself from siblings such as get_echoo_documentation or get_echoo_pricing, which plausibly overlap.

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 explicit when-to-use statement, no when-not-to-use exclusion, and no named alternative among the sibling tools. The phrase "public product catalog" only weakly implies a scope contrast with documentation and pricing lookups, leaving the routing decision to inference.

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