Edwin by theButler.network

Product summary and key features

get_product_text

Read-only

Edwin's short summary and key features for products from an earlier Edwin result (search_products, recommend_product, find_alternatives, compare_products or get_offers), written from the merchants' product data, not from tests or reviews. Use it when the user asks what a product offers, what is included, or how the products differ.

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": {
      "pids": "<pids>",
      "market": "<market>",
      "lang": "<lang>"
    },
    "name": "get_product_text"
  }
}

Input Schema

Name	Required	Description
`lang`	Yes	Language of the summary as a BCP 47 tag, e.g. de-DE, en, pt-BR: the language the user writes in.
`pids`	Yes	Product ids from a previous Edwin tool result, at most eight.
`market`	Yes	ISO 3166-1 alpha-2 country code of the user's shopping market, e.g. DE, AT, NL, FR, GB, US. Infer from the user's context.

Output Schema

Name	Required	Description	Default
`lang`	Yes
`texts`	Yes
`market`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this as a non-destructive, closed-world read, so the safety profile is covered. The description adds genuinely new behavioral context: the content is written from merchants' product data rather than tests or reviews, which tells the agent how much to trust the summaries. It does not discuss latency, caching, or behavior when pids are stale.

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?

Two sentences, front-loaded with what the tool returns before stating when to use it. The parenthetical list of five sibling tools is the longest element, but it earns its place by defining where pids may come from.

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 needn't explain return values, and annotations plus full schema coverage handle safety and parameters. What remains is covered: purpose, source, and trigger are all stated, leaving only edge cases such as invalid or stale pids unaddressed.

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%, so the baseline is 3: lang, pids, and market are all documented with formats and examples. The description only restates the provenance constraint already present in the pids schema ('from an earlier Edwin result'), adding no new format or interpretation guidance.

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

Purpose5/5

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

The description names a specific resource (short summary and key features for products) and a precise provenance (derived from merchants' product data, not tests or reviews). It also enumerates the sibling tools whose results supply the product ids, so an agent can tell this apart from get_offers or compare_products without opening the schema.

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?

It gives an explicit trigger: 'when the user asks what a product offers, what is included, or how the products differ,' and states the prerequisite that pids must come from an earlier Edwin result. It stops short of an explicit when-not clause, and 'how the products differ' overlaps with the compare_products sibling, leaving a small routing ambiguity.

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

All Edwin by theButler.network 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?