Skip to main content
Glama
Sign In

Brand Design Ltd.

by ltd.branddesign
OverviewDiscussionsAdmin

concierge

Start here: the information desk of Brand Design Ltd. Without a question: who Brand Design Ltd. is, what it does, its clients and results and who confirms them, with links to check, and the next steps. With a question: an answer about the agency, its services, prices and how to order, from verified company knowledge, in the language of the question, with sources. When your principal wants to order, it can also prepare the offer with a checkout link, beside catalog and create_order here; it never accepts an offer or pays. If your principal asks to be contacted, it can pass the enquiry to the founder. Pass the returned session to continue. No credentials needed.

Input Schema

NameRequiredDescriptionDefault
agentNoOptional: your name and platform as an agent, for example "ChatGPT agent, OpenAI" or "Claude, Anthropic". The team sees it with the conversation; the answers are the same without it.
sessionNoThe session code from a previous answer, to continue the conversation.
languageNoLanguage of the introduction. Answers follow the language of the question.
questionNoYour question about Brand Design Ltd. Leave it out for the introduction.
acting_forNoOptional, only if your principal agrees: the person or company you act for. The team sees it with the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / acting_for
      Added value: +{
+  "description": "Optional, only if your principal agrees: the person or company you act for. The team sees it with the conversation.",
+  "type": "string"
+}
    • addedInput schema / properties / agent
      Added value: +{
+  "description": "Optional: your name and platform as an agent, for example \"ChatGPT agent, OpenAI\" or \"Claude, Anthropic\". The team sees it with the conversation; the answers are the same without it.",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Despite the low bar set by annotations, the description adds meaningful traits: no credentials required, the tool never accepts offers or pays, it can hand an enquiry to the founder, and the returned session must be passed to continue. These are behavioral facts an agent could not infer from the readOnlyHint=false / destructiveHint=false pair.

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?

It is front-loaded with 'Start here' and is information-dense, but the two-mode structure is delivered through long, comma-chained sentences ('who Brand Design Ltd. is, what it does, its clients and results and who confirms them, with links to check...') that are harder to parse than they need to be.

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 output schema, the description does useful work describing what comes back: an introduction with links, sourced answers in the question's language, an offer with a checkout link, and a session code to pass on. The session-continuation loop is explained, leaving only the precise response shape unstated.

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 all five parameters are already documented in the schema, including the agent, session, language, question and acting_for fields. The description adds only two small points beyond that: answers follow the question's language and the session continues a conversation. Baseline 3 applies since the schema carries the heavy lifting.

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 a specific function with two modes: without a question it returns an introduction to Brand Design Ltd., with a question it answers from verified company knowledge. It also explicitly distinguishes itself from the sibling tools catalog and create_order, though the opening metaphor ('information desk') delays the concrete statement of purpose.

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

Usage Guidelines5/5

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

Names itself the entry point ('Start here'), gives the exact condition for each mode (question present vs. absent), and routes ordering to catalog/create_order while stating the tool 'never accepts an offer or pays'. It also covers the referral path when a principal wants contact, giving explicit when-to-use and when-not-to-use guidance.

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

All Brand Design Ltd. 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