SalesHookAI

Suggest technician

suggestTechnicianForProject

Read-onlyIdempotent

Suggests which team member could take a project on a given date: who is available (not on vacation, not booked elsewhere), ranked by estimated extra travel distance. Read only; does not create an assignment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggestTechnicianForProject"
  }
}

Input Schema

Name	Required	Description
`date`	No	Date in YYYY-MM-DD format to check availability for; defaults to the project's start date or today
`projectId`	No	Numeric project ID
`projectName`	No	Project name (resolved to ID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces rather than contradicts them with 'Read only.' It adds real value beyond the annotations by defining availability (not on vacation, not booked elsewhere) and disclosing the ranking criterion, which the annotations cannot convey.

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 the core action and candidate criteria front-loaded and the non-mutating guarantee last. Every clause carries information; nothing is repeated from the title or schema.

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 a three-parameter, zero-required read tool with full schema coverage and no output schema, the description covers purpose, eligibility rules, ranking, and side-effect profile. The only gap is the exact shape of the suggestion result (for example, whether it returns a ranked list or a single best candidate), which the description leaves for the agent to discover.

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 coverage is 100%, with the date format, default resolution, and project ID/name resolution all documented in the schema. The description only echoes 'on a given date' and adds no format or precedence detail beyond what the parameter descriptions already supply, so the baseline of 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?

The description names a specific verb (suggests), the resource (team member for a project on a given date), and the ranking criterion (estimated extra travel distance). It also explicitly separates itself from assignment-creating siblings with 'does not create an assignment,' so an agent can place it without opening a schema.

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?

The opening clause states the concrete situation for use: finding a candidate for a project on a given date. The closing 'does not create an assignment' implicitly routes the agent to a create/assignment tool when it actually wants to commit, but no alternative tool is named and no exclusion beyond that is spelled out.

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

All SalesHookAI 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?