Skip to main content
Glama

Goce Petrov, brand designer

by com.gocepetrov
OverviewDiscussionsAdmin

Draft an intro message

request_intro
Read-onlyIdempotent

Builds a ready-to-send intro message and a link the person opens to send it themselves (WhatsApp, email) or a booking link (Calendly). This server does not send the message. Do not put personal data (names, phone numbers, emails) in the summary. Conversations with this agent are kept for up to 12 months so Goce can improve it: the messages, the time, the app used and an approximate location (country, city, network). No IP addresses are stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoHow the person wants to reach Goce: a WhatsApp or email link, or a Calendly booking linkwhatsapp
companyNoCompany or product name
summaryYesOne or two sentences about the project, no personal data
languageNoLanguage of the message: English or Frenchen
project_typeYesThe service that fits, by id from get_services, or other

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
noteYes
channelYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_type / enum
      Previous value: -[
-  "next-stage-sprint",
-  "brand-sprint",
-  "brand-system-website",
-  "brand-automation",
-  "ai-for-design-teams",
-  "ai-agents-sites",
-  "other"
-]New value: +[
+  "next-stage-sprint",
+  "brand-sprint",
+  "brand-system-website",
+  "brand-automation",
+  "ai-for-design-teams",
+  "read-check",
+  "tool-copy",
+  "in-chat-design",
+  "other"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / channel / description
      Added value: +"How the person wants to reach Goce: a WhatsApp or email link, or a Calendly booking link"
    • addedInput schema / properties / company / description
      Added value: +"Company or product name"
    • addedInput schema / properties / language / description
      Added value: +"Language of the message: English or French"
    • addedInput schema / properties / project_type / description
      Added value: +"The service that fits, by id from get_services, or other"
  3. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare it read-only/idempotent, but the description goes well beyond them: it discloses that no message is actually sent (the key behavioral surprise), imposes a PII constraint, and details data retention (12 months), what is logged (messages, time, app, approximate location), and that no IPs are stored. This is unusually rich behavioral context.

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?

Three sentences, front-loaded with the deliverable and the key 'does not send' caveat. The retention sentence is long but carries legally meaningful detail. No filler, though the privacy sentence could be tightened.

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, return values need not be described, and annotations cover safety. The description supplies the non-sending behavior and privacy posture. The main gap is routing guidance relative to the other six sibling tools, which is omitted.

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% (channel, language, project_type, company, summary all documented with enums/defaults). The description only reinforces the PII constraint on 'summary', which the schema already states, so it adds little beyond structured data. Baseline 3 applies.

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?

States a specific verb and resource ('Builds a ready-to-send intro message') plus the concrete artifacts returned (WhatsApp/email link, Calendly booking link). It also clarifies a non-obvious boundary ('This server does not send the message'). It does not name any sibling (e.g. submit_brief), so differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied by the outputs described and the 'do not put personal data in the summary' constraint, which is actionable guidance. However, there is no statement of when to choose this over siblings like submit_brief or ask_goce_agent, and no preconditions for calling it.

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

All Goce Petrov, brand designer 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