SameDayDesk agent tools

check_agent_readiness

Read-onlyIdempotent

Free. Check whether agents can discover and call a public website. Fetches discovery files, follows MCP links named by those files, and runs only initialize, tools/list, and one unknown-tool call. Never executes a real tool. Returns a 0-100 score, every check with an evidence URL, and the top fixes. No license.

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": {
      "host": "<host>"
    },
    "name": "check_agent_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Public host to score, for example example.com

Output Schema

Name	Required	Description	Default
`free`	No
`host`	Yes
`score`	Yes
`checks`	Yes
`evidence`	Yes
`topFixes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), yet the description adds meaningful behavior: the exact bounded probe sequence (initialize, tools/list, one unknown-tool call), the explicit guarantee that no real tool is ever executed, and the return shape (0-100 score, per-check evidence URLs, top fixes). This is exactly the added context annotations cannot supply.

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 tight sentences, front-loaded with cost and scope, then the exact operations, then the return contract. No sentence is filler; even the fragment 'No license.' conveys a distinct constraint.

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?

An output schema exists, so return values need not be re-explained, and the description still summarizes them. Combined with the explicit probe limits and public-host requirement, an agent has nearly everything needed; only sibling differentiation 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 coverage is 100% and the single 'host' parameter is fully documented with an example. The description reinforces that the target must be a public website/host but adds no syntax, format, or constraint detail beyond the schema.

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 ('Check whether agents can discover and call a public website') and enumerates the exact operations performed. It is clear on its own, but never distinguishes itself from the sibling check_ai_readiness, which an agent must disambiguate by name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by the purpose statement and by 'Free'/'No license,' which hints this is the low-cost option versus a paid sibling. There is no explicit when-to-use/when-not guidance and no sibling tool is named as an alternative.

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

All SameDayDesk agent tools 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.