Skip to main content
Glama
Sign In
@millwork/solver-mcp

@millwork/solver-mcp

Official
by millworkdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

solver_poll_source_handoff

Poll a credential handoff intent to check if the human has completed it in the browser. Returns the current intent state.

Instructions

Poll a credential handoff intent until the human completes it in the browser (GET /v1/source-credential-handoffs/{handoff_intent_id}). Answers the intent state only.

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": {
      "handoff_intent_id": "<handoff_intent_id>"
    },
    "name": "solver_poll_source_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
handoff_intent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a read-only GET operation and that only the intent state is returned. However, it does not clarify whether a single call blocks or returns immediately, whether repeated polling is required, or what the possible state values are.

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?

The description is only two sentences, front-loaded with the core action and resource. The endpoint is placed in parentheses as supporting detail, and the 'state only' note adds important clarification without padding.

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

Completeness3/5

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

For a single-parameter polling tool with no output schema and no annotations, the description gives the main purpose and endpoint but omits operational essentials: how to obtain the handoff_intent_id, how polling terminates, and what state values will be returned. This leaves some necessary inference to the agent.

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 0%, so the description must compensate. It does show handoff_intent_id being used in the endpoint path, which helps, but it does not explain where the ID comes from, such as the result of solver_start_source_handoff, or any format expectations.

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 states a specific verb and resource: 'Poll a credential handoff intent.' The endpoint and the clarifying phrase 'Answers the intent state only' make it clear this is a status-read operation, not a mutation or creation tool, distinguishing it from siblings like solver_start_source_handoff.

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 phrase 'until the human completes it in the browser' clearly conveys when this tool is relevant: after a handoff intent has been started and the agent is waiting on user action. It does not explicitly name the prerequisite tool or provide when-not-to-use guidance, but the context is reasonably clear.

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

Deploy Server

Other Tools