Skip to main content
Glama

AgentSynta Business Beacon

Submit inquiry

submit_inquiry
Destructive

Send a customer inquiry to a business for human review. Cannot place orders or change prices; only use with the customer's consent.

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": {
      "slug": "<slug>",
      "contact_name": "<contact_name>",
      "contact_email": "<contact_email>",
      "message": "<message>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug, e.g. 'harbor-bean'. Use list_businesses to find one.
messageYes
subjectNo
agent_nameNoName of the assistant submitting.
offering_idNoOptional offering id from search_offerings.
contact_nameYes
contact_emailYes
contact_phoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true, destructiveHint=true and non-idempotent, so the agent knows this has external, irreversible side effects. The description adds the consent requirement and the order/price exclusions, but says nothing about what actually happens on submission (record created, message delivered, duplicate submissions possible) beyond what the hints imply.

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?

Two short sentences with zero filler, front-loading the action and then the constraints. Every clause carries information.

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

Completeness2/5

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

For an 8-parameter, non-idempotent, externally visible write tool with no output schema, the description is thin: it does not explain what a successful submission yields, whether the offering_id links the inquiry to a listing, or which contact fields are used for the business's reply. An agent could call it, but with real uncertainty about inputs and outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38% across 8 parameters, and the description mentions none of them — not contact_name, contact_email, message, subject, agent_name, nor offering_id. With half the fields undocumented in the schema, the description does nothing to compensate for the coverage gap.

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 ('Send a customer inquiry to a business') plus the disposition ('for human review'), which distinguishes it from the read-only siblings like get_business_profile and search_offerings. It stops short of naming any sibling as an alternative, so it is clear but not fully differentiated.

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 real precondition ('only use with the customer's consent') and an explicit scope exclusion ('Cannot place orders or change prices'), which tells the agent when this tool is and is not appropriate. It does not name a competing tool for the excluded order/price actions, leaving a small inference gap.

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