Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

websearch__deps

npm dependency risk check for a package. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/websearch/deps

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "websearch__deps"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / packages
      Removed value: -{
-  "type": "string"
-}
  2. Changed6 schema fields changed
    • removedInput schema / properties / chars
      Removed value: -{
-  "description": "Markdown chars per page (200-8000)",
-  "type": "integer"
-}
    • removedInput schema / properties / extract
      Removed value: -{
-  "description": "How many hits get full text (0-5)",
-  "type": "integer"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Max results (1-25)",
-  "type": "integer"
-}
    • addedInput schema / properties / packages
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / q
      Removed value: -{
-  "description": "Search query",
-  "type": "string"
-}
    • removedInput schema / properties / url
      Removed value: -{
-  "description": "Single URL to convert to markdown instead of searching",
-  "type": "string"
-}
  3. Changed7 schema fields changed
    • addedInput schema / properties / chars
      Added value: +{
+  "description": "Markdown chars per page (200-8000)",
+  "type": "integer"
+}
    • addedInput schema / properties / extract
      Added value: +{
+  "description": "How many hits get full text (0-5)",
+  "type": "integer"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (1-25)",
+  "type": "integer"
+}
    • removedInput schema / properties / packages
      Removed value: -{
-  "description": "Comma-separated npm package names",
-  "type": "string"
-}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Search query",
+  "type": "string"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Single URL to convert to markdown instead of searching",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "packages"
-]
  4. Changed2 schema fields changed
    • removedInput schema / properties / ecosystem
      Removed value: -{
-  "description": "Package ecosystem (default npm)",
-  "enum": [
-    "npm"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / packages / description
      Previous value: -"Comma-separated package names, optionally name@version"New value: +"Comma-separated npm package names"
  5. Changed3 schema fields changed
    • addedInput schema / properties / ecosystem
      Added value: +{
+  "description": "Package ecosystem (default npm)",
+  "enum": [
+    "npm"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / packages / description
      Added value: +"Comma-separated package names, optionally name@version"
    • addedInput schema / required
      Added value: +[
+  "packages"
+]
  6. Added

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the most critical behavioral trait: the tool is paid ($0.01 USDC on Base eip155:8453) and requires an x402 payment passed in params._meta["x402/payment"]. That auth/payment requirement is exactly the kind of context an agent needs before invoking. It still omits what the risk result contains and error/failure behavior, so not a 5.

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

Conciseness4/5

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

Purpose is front-loaded in the first clause, followed by payment terms, with no wasted wording. The HTTP endpoint line is arguably redundant for an MCP invocation but is compact service metadata rather than noise.

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 one-parameter tool with no output schema and no annotations, the definition covers purpose, price, and payment mechanism. It is still incomplete on what a 'risk check' actually returns (vulnerabilities, outdated deps, licenses) and how failures are surfaced, which matters for a paid call.

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 0% with one undocumented 'name' parameter. The phrase 'for a package' implies name is the npm package identifier and the description surfaces a hidden payment field (params._meta) absent from the schema, which adds real value. However, format details (scoped packages like @scope/name, version pinning) and the odd optionality (0 required params) are left unexplained.

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+resource: 'npm dependency risk check for a package'. This is clearly distinct from siblings like websearch__search or websearch__dossier. It stops short of explicitly contrasting itself with those siblings, but the resource is concrete enough for an agent to select it.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The description says what the tool does but never tells the agent under what circumstances to prefer it over websearch__dossier or websearch__search. Usage must be inferred entirely.

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

All automaton toolsInspect
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.

Resources