Skip to main content
Glama

Market Brew

Summarize unresolved crawl seed errors

summarize_deep_crawl_seed_errors
Read-onlyIdempotent

Use this when the user asks to summarize unresolved crawl seed errors. Returns only data visible to the linked Market Brew account.

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": {
      "website": "<website>"
    },
    "name": "summarize_deep_crawl_seed_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / website / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a scoping constraint beyond the annotations ("Returns only data visible to the linked Market Brew account"), which is genuinely useful. It does not define what makes an error "unresolved" or what the summary contains.

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

Conciseness3/5

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

Two short sentences with no filler, which is good. However, the first sentence is largely a restatement of the title, so it consumes the prime front-loaded position without adding new information.

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

Completeness2/5

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

A simple read tool with no output schema, so the description should compensate by explaining the output shape and the required website identifier. Neither is covered; with 0% parameter coverage and ambiguous types, the definition is under-specified for correct invocation.

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

Parameters2/5

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

One required parameter (website) with 0% schema description coverage and an ambiguous anyOf of integer ID, numeric string, or up-to-254-char string. The description says nothing about this parameter, so the agent cannot tell whether to pass an ID, a domain, or a URL. Meaning beyond the schema is effectively zero.

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 ("summarize unresolved crawl seed errors") and the intent is clear. It does not differentiate from the sibling export_deep_crawl_seed_errors, so an agent must guess whether the user wants a summary or an export.

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?

Provides a single triggering condition ("Use this when the user asks to summarize unresolved crawl seed errors"), which is essentially a restatement of the tool name. No when-not guidance, no prerequisites, and no mention of the export sibling as an alternative for raw data.

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