Skip to main content
Glama

Extract Evidence

tb_extract

Extract claim outcomes from web pages by checking each claim against page content and returning citations with confidence bands. Supports both stateless URL extraction and active browser tab.

Instructions

Extract claim outcomes from a target or opened daemon tab. In a session, omit target to use the active opened tab; claims is always required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoThe URL or target whose evidence should be extracted. Required for stateless extraction; optional when sessionId points at an opened active tab.
claimsYesRequired list of claims to verify against the target or active opened tab and support with citations when possible.
browserNoWhen true, use the browser-backed acquisition path for this operation.
budgetNoToken budget for snapshot and semantic processing. Default is 512.
mainOnlyNoWhen true, extract only from the page's main content.
verifierCommandNoAn optional verifier command to run for this operation.
sourceRiskNoThe source risk label to attach to the result or citation.
sourceLabelNoThe human-readable source label to attach to the result or citation.
allowDomainsNoRestrict the operation to this list of allowed domains.
sessionIdNoThe browser session to use for this operation.
tabIdNoThe specific tab to use inside the session. If omitted, the active tab is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
openNo
extractNo
sessionStateNo
sessionIdNo
tabIdNo
diagnosticsNo
resultNo
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It implies a read/analysis operation (extract), mentions citation support, but does not disclose potential side effects, authentication needs, or rate limits. Some context is given but missing important details for a tool with many parameters.

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 two sentences, front-loaded with the main purpose, and includes key usage guidance without extraneous detail. Every sentence earns its place.

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?

Given the tool's complexity (11 parameters, 1 required) and the presence of an output schema, the description adequately covers the core function and key parameter relationships. It could elaborate on what 'extract claim outcomes' entails, but is complete enough for selection.

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 baseline is 3. The description adds value by explaining the target-session relationship and re-stating claims requirement, but does not enrich other parameters (browser, budget, etc.) beyond their schema descriptions.

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 clearly states the verb 'Extract' and the resource 'claim outcomes from a target or opened daemon tab'. It distinguishes from sibling tools (e.g., tb_read_view, tb_search) which have different purposes.

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?

Provides clear context on when to omit target (in a session with active tab) and emphasizes that claims is always required. Does not explicitly exclude alternatives, but sibling tools are distinct enough to imply usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nangman-infra/touch-browser'

If you have feedback or need assistance with the MCP directory API, please join our Discord server