Skip to main content
Glama

Poll a browser-agent task

browse_status
Read-only

Check a browsing task’s status to get its current state, or retrieve the final answer and agent steps once available; each check takes about a second and is free.

Instructions

Poll a task browse started: its state, or the answer and the agent's steps once it has one. Free, about a second.

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": {
      "handle": "<handle>"
    },
    "name": "browse_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe handle a `browse` call handed back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior — no cost and roughly one-second latency — and tells the agent what the payload contains (state, or answer plus agent's steps). It doesn't say what states exist or whether polling must be repeated until a terminal condition, which would be the most valuable remaining detail.

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?

A single sentence that leads with the action and resource, then the return shape, then cost and latency. Nothing is padded and no clause is redundant.

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?

With no output schema, the description carries the burden of describing return values and does so compactly (state, answer, steps). For a one-parameter read-only polling tool the only real gap is the absence of terminal-state or polling-loop guidance.

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?

Only one parameter and schema coverage is 100%, so the schema already explains that `handle` is the value a `browse` call returned. The description's 'a task `browse` started' reinforces provenance but adds no format or lifecycle detail beyond the schema. Baseline 3 applies.

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 concrete verb (poll) and resource (a task started by `browse`), plus what the response contains — state, or answer and agent steps. It ties itself to the `browse` sibling by name, making the pairing obvious, but doesn't explicitly contrast with other status-polling siblings like research_status or budget_status.

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?

Clear implied workflow: call this after a `browse` call hands back a handle. 'Free, about a second' gives useful cost/latency context for deciding poll cadence. It stops short of stating when to stop polling or what terminal states look like, so no exclusions are offered.

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