Argus

Overview Schema Source Related Servers Discussions Admin

search_web

Run web searches through Argus's authenticated search broker, returning ranked results with provider fallback and budget enforcement.

Instructions

Search through the authenticated Argus HTTP authority.

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": {
      "query": "<query>"
    },
    "name": "search_web"
  }
}

Input Schema

Name	Required	Default
`mode`	No	discovery
`query`	Yes
`caller`	No	mcp
`free_only`	No
`session_id`	No
`max_results`	No
`include_attribution`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.2May 24, 2026

addedInput schema / properties / caller

Added value: +{
+  "default": "mcp",
+  "title": "Caller",
+  "type": "string"
+}

addedInput schema / properties / free_only

Added value: +{
+  "default": false,
+  "title": "Free Only",
+  "type": "boolean"
+}

addedInput schema / properties / include_attribution

Added value: +{
+  "default": false,
+  "title": "Include Attribution",
+  "type": "boolean"
+}

First observedv0.1.0Apr 5, 2026

TDQS

C2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing. The single useful signal is the word 'authenticated', implying credentials are required, but there is no mention of rate limits, result set size, mode semantics, or what 'free_only' gates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence is technically tight, but this is under-specification rather than conciseness. Brevity earns no credit when the result leaves a 7-parameter tool effectively undocumented.

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

Completeness1/5

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

The output schema means return values need not be explained, but that is the only burden lifted. With no annotations, seven undocumented parameters, and no disambiguation from search_web_v2, the definition is nowhere near complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes 7 parameters at 0% schema description coverage, and the description adds no meaning to any of them. 'mode', 'caller', 'free_only', and 'include_attribution' are completely undefined in both structured and natural-language form.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a verb ('Search') and a resource ('the authenticated Argus HTTP authority'), so it is not a pure tautology. But 'Argus HTTP authority' is opaque jargon, and it never distinguishes this tool from the sibling 'search_web_v2', which an agent would naturally confuse it with.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool, when not to, or which sibling to prefer. The presence of 'search_web_v2' in the sibling list makes the absence of routing guidance a real problem, not a minor omission.

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

Deploy Server