Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Classify cookies via Open Cookie Database

web-technology_cookie-inventory-classify
Read-onlyIdempotent

Categorise cookies using exact and wildcard matches against the Open Cookie Database. Price $0.03 USDC. POST /api/v1/web-technology/cookie-inventory-classify. An unpaid call returns the x402 payment terms and does not run.

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": {
      "cookies": "<cookies>"
    },
    "name": "web-technology_cookie-inventory-classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
cookiesYescookies, array. Required.

Output Schema

NameRequiredDescriptionDefault
cookiesNocookies. Array.
sourcesNosources. Array.
summaryNosummary. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds genuinely useful behavior beyond them: the $0.03 USDC price, the concrete endpoint, and the critical fact that an unpaid call returns x402 payment terms without executing. It does not resolve match precedence (exact vs wildcard) on conflicts, which would be the remaining valuable disclosure.

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?

Three short sentences, front-loaded with the purpose, followed by price, endpoint, and the payment-failure behavior. Every sentence carries information; the raw endpoint string is the least essential element but supports the payment context.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. The description completes the picture with cost and payment-gating behavior, which is the non-obvious risk for a caller. It is complete enough to invoke correctly, with only match-precedence semantics left unstated.

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 100% and the single cookies array documents name (required, min length 1) and domain (optional) with nested field descriptions. The description adds nothing about parameter meaning; the mention of exact/wildcard matching hints at why domain matters but does not explain it. Baseline 3 applies when the schema does the work.

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 names a specific verb (categorise), a specific resource (cookies), and the matching mechanism (exact and wildcard matches against the Open Cookie Database). No sibling in the list performs cookie classification, so an agent can route to it unambiguously.

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

Usage Guidelines3/5

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

Usage is only implied: it is clearly the tool for classifying cookies, but there is no statement of when to prefer it, what input it expects at a business level, or what to do with the results. No alternatives or exclusions are offered, leaving the agent to infer context from the verb alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources