Skip to main content
Glama

Contact the Developh team

request_contact

Sends a project inquiry or question to the Developh team with the person's own name, email and message. It writes: it creates an inquiry and emails the person a confirmation. The team usually replies by email within 2 to 8 business hours. Requires confirmed=true, which records that the person reviewed the message and asked for it to be sent.

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": {
      "name": "<name>",
      "email": "<email>",
      "message": "<message>",
      "confirmed": "<confirmed>"
    },
    "name": "request_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name, as they gave it.
emailYesThe person's own email address. The confirmation and the reply go here.
phoneNoPhone number, only if they gave it.
localeNoAnswer language: English (en) or European Portuguese (pt).en
companyNoCompany or business name, if they gave one.
messageYesWhat they need, in their words: the project, goals, timeline and budget if known.
confirmedYesRecords that the person reviewed the message and asked for it to be sent. Must be true.
availabilityNoWhen they can take a first call, e.g. weekday mornings, Lisbon time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirmed / description
      Previous value: -"True only after the person reviewed the message and asked you to send it."New value: +"Records that the person reviewed the message and asked for it to be sent. Must be true."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the call writes a record and emails the person a confirmation, quotes an expected reply window of 2–8 business hours, and explains the confirmed=true gate as a record of human consent. The annotations already flag readOnly=false and openWorld=true, but the description supplies the concrete side effects and downstream timing an agent needs.

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?

Four short sentences, front-loaded with the core action before side effects, timing and the consent gate. Each sentence carries distinct information with no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no output schema and eight fully documented parameters, the description covers the action, the side effects, the expected turnaround and the consent requirement. Nothing an agent needs in order to call this correctly is missing.

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 every parameter is already documented in the schema. The description restates name, email and message and paraphrases the confirmed gate, adding no format, constraint or edge-case meaning beyond the structured data – baseline 3 applies.

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?

States a specific verb and resource – sending a project inquiry or question to the Developh team – and names the payload it carries (name, email, message). It is unmistakably different from the siblings list_case_studies, run_website_audit and studio_info.

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?

Frames the use case as a project inquiry or question and adds the precondition that confirmed=true must be set, which tells the agent when the call is legitimate. It does not explicitly name when not to use it or route to a sibling, but the siblings cover unrelated functions so no confusion is likely.

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