Skip to main content
Glama

Market Brew

Get explicit crawl schedule

get_deep_crawl_schedule
Read-onlyIdempotent

Use this when the user asks to get explicit crawl schedule. 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": "get_deep_crawl_schedule"
  }
}

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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The one genuine addition is the access scoping ('Returns only data visible to the linked Market Brew account'), but nothing is said about whether the schedule can be empty, whether it is per-website or global, or how it behaves for an unconfigured site.

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, but the first sentence carries almost no information and the sizing is minimal for a tool with an undocumented parameter. Front-loading is fine; substance is not.

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?

Considered as a simple single-parameter read tool with no output schema, the definition is nearly complete for correct invocation — the missing piece is the meaning/format of the website argument, which is a real but bounded gap.

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?

There is a single required parameter, website, with 0% schema description coverage, and the schema's anyOf (integer ID or string domain, max 254 chars) is genuinely ambiguous. The description does not explain which identifier form is expected or how a website maps to a schedule, so it fails to compensate for the coverage gap.

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 restates the name/title ('get explicit crawl schedule') rather than explaining what an 'explicit crawl schedule' actually is, what it contains, or how it relates to the deep-crawl seed/inventory siblings. A verb+resource is identifiable, but the scope is left vague.

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?

'Use this when the user asks to get explicit crawl schedule' is circular guidance that offers no real when-to-use condition and no distinction from siblings like get_deep_crawl_seed or list_deep_crawl_inventory_versions. No exclusion or alternative is named.

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