Skip to main content
Glama

Innovative Workspace

Send IW a short brief

submit_contact

Send Innovative Workspace a short brief, as the contact form on its site does: name, work email and organisation are required, the rest is optional. It is a dry run (checks the brief, sends nothing) unless dry_run is false. Only include details the person gave you and agreed to share.

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>",
      "organisation": "<organisation>"
    },
    "name": "submit_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
helpNoWhat would you like help with? (optional): one of the form's choices.
nameYesName: up to 100 characters.
timeNoWhat takes your team the most time today? (optional): line breaks allowed, up to 3,000 characters.
typeNoType of organisation (optional): one of the form's choices.
whenNoWhen suits you for a call? (optional): a few days and times that suit, and the time zone, up to 300 characters.
emailYesWork email: the person’s work email address, up to 254 characters.
heardNoHow did you hear about us? (optional): one of the form's choices.
staffNoNumber of staff (optional): one of the form's choices.
countryNoCountry (optional): one of the form's choices.
dry_runNoLeave it out (or true) to check the brief and see what would be sent. false sends it, but only if this server has sending turned on.
organisationYesOrganisation: up to 150 characters.

Output Schema

NameRequiredDescriptionDefault
okYes
sentYes
dryRunYes
errorsNo
statusNo
messageYes
requestNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description adds the far more important fact that the call is a no-op by default and only transmits when dry_run is false AND the server has sending enabled. It also discloses the data-handling constraint, which no annotation conveys.

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 short sentences, front-loaded with the purpose and the default dry-run behaviour. The "as the contact form on its site does" analogy is mildly redundant with the field list that follows, but it is not wasteful enough to hurt.

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?

For an 11-parameter, enum-heavy submission tool with an output schema and annotations present, the description covers the two things an agent cannot infer: that the default is a safe dry run and that consent governs field population. It omits what the dry-run check actually reports, but the output schema is expected to cover that.

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% and every parameter already carries its own description, so the schema does the heavy lifting. The description adds the required-versus-optional split, which is already encoded in the schema's required array, plus the consent filter on values. Baseline 3 is appropriate.

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 ("Send Innovative Workspace a short brief") and pins down the exact shape of the payload: name, work email and organisation required, the rest optional. An agent can immediately distinguish this outbound-submission tool from the read-only lookup siblings such as get_pricing or search_faqs.

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?

Gives a clear operating condition – the brief is a dry run unless dry_run is false – and a consent rule ("Only include details the person gave you and agreed to share"). It stops short of explicitly saying when to prefer this tool over simply answering from the other tools, but the submission framing makes the boundary reasonably obvious.

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