Nikola Dikic - Full-Stack Developer, WordPress, WooCommerce, ERP Integrations

submit_project_inquiry

Describe a project in writing and get a reply within 24 hours, weekends included. For work that is planned rather than broken: a rebuild, a migration, an integration, a second opinion on code somebody else wrote. Use submit_urgent_request instead when a site is down or losing money now. Submits immediately, so ask the person first and send their real email address.

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

Input Schema

Name	Required	Description
`name`	Yes	Their name.
`site`	No	Optional. The site in question.
`email`	Yes	Their email. The reply goes here, so it must be theirs and correct.
`company`	No	Optional.
`message`	Yes	The shape of the work, in their words. Platform, what exists today, what they want, any deadline or budget band.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation profile is partly covered; the description adds that it 'submits immediately' (no confirmation step, non-idempotent in practice) and that the email must be the real person's, plus a 24-hour response SLA. It stops short of stating whether a duplicate submission creates a second inquiry or what happens on failure.

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?

Three sentences, front-loaded with the outcome and SLA, then the qualifying use case, then the routing rule and the consent warning. No filler or 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?

No output schema exists, yet the description tells the agent what to expect back (a reply within 24 hours, weekends included). Combined with 100% parameter coverage and explicit sibling routing, nothing an agent needs 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 all five parameters (name, site, email, company, message) are already documented. The description reinforces the email constraint ('must be theirs and correct'), but adds no syntax, format, or validation detail beyond what the schema provides, so the 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 concrete verb+resource ('Describe a project in writing and get a reply') plus the concrete outcome (reply within 24 hours, weekends included). It also draws a hard line against the sibling submit_urgent_request, so an agent can route without opening either schema.

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?

Explicitly names the alternative ('Use submit_urgent_request instead when a site is down or losing money now') and characterizes the qualifying work with examples: rebuild, migration, integration, second opinion. Both when-to-use and when-not-to-use are present.

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

All Nikola Dikic - Full-Stack Developer, WordPress, WooCommerce, ERP Integrations tools Inspect

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

Need Help?