Skip to main content
Glama
Sign In

Faire MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Reply to message in Faire

faire_reply_to_message
Read-onlyIdempotent

Reply to message in the user's own Faire account from ChatGPT, Claude or any AI agent. Returns how to do it in Faire step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Faire Cloud Browser. Faire's official API: Yes, but only part of it: Faire has an External API for brands that covers products, orders and inventory, and a single brand can generate its own access token in the brand portal (checked 11 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Adds meaningful context beyond the annotations by declaring 'opens nothing by itself' and that it returns screens, buttons and fields, which reinforces the readOnlyHint=true and openWorldHint=false claims rather than contradicting them. However, it gives no sense of output shape, length, or freshness of the returned guide, and the dated API note reads like boilerplate rather than behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core value is front-loaded ('Reply to message... Returns how to do it step by step... opens nothing by itself'), but 'from ChatGPT, Claude or any AI agent' is filler and the API paragraph consumes roughly half the text with content unrelated to replying to messages. Trimming that paragraph would sharpen the definition considerably.

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 no parameters, no output schema, and annotations already covering the safety profile, the description gives the agent what it needs: what it returns, that it performs no action, and which tools execute the reply. A brief note on what the returned steps look like would make it complete.

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 nothing for the description to disambiguate; baseline applies. The description correctly implies no arguments are needed by describing a parameterless lookup-and-guide operation.

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?

Names a specific verb and resource ('Reply to message in the user's own Faire account') and immediately clarifies the actual output is a step-by-step guide rather than a performed action, which separates it from the cotlet_browser_* execution tools. The trailing sentence about Faire's External API (products, orders, inventory) is unrelated to messaging and blurs the purpose slightly.

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?

States the workflow explicitly: this tool returns the how-to, then the agent must act using cotlet_browser_* tools in the user's Faire Cloud Browser. That is a clear handoff to the correct alternative. It stops short of stating exclusions (e.g., when an existing browser session already has the thread open), so not a 5.

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

All Faire MCP Server and API by Cotlet toolsInspect
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