Skip to main content
Glama

prepare_search

Define and store a bounded LinkedIn job search plan with titles, locations, result and cost caps, and source, without making a paid call so you can review scope first.

Instructions

Prepare and store a bounded search plan. No paid call. Disclose the source and caps in chat.

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": {
      "brief": "<brief>"
    },
    "name": "prepare_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYes
sourceNoapify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Adds real context beyond annotations: no paid call is made, a plan is persisted, and the source/caps must be surfaced to the user. Annotations already flag non-read-only but non-destructive behavior, so the incremental value is the cost/safety framing. It doesn't say what gets overwritten if a plan already exists or where the plan is stored.

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 verb and resource, no filler. Slightly telegraphic phrasing ('bounded', 'caps') that assumes the reader knows the schema.

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 stateful preparation tool with a nested brief object containing 8 fields and zero schema descriptions needs far more coverage than three sentences. With no output schema, the agent also gets no hint of what identifier or status the stored plan returns.

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?

Schema description coverage is 0%, so the description must carry parameter meaning and it does not. It never mentions 'brief', 'source', the caps (max_results, max_charge_usd), or defaults, despite these being the substantive fields.

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?

Description states a specific action (prepare and store a bounded search plan) plus a cost guarantee (no paid call). It distinguishes itself from search_jobs by being a preparation step, though it never names the sibling that actually executes the search.

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?

Implied workflow is clear: prepare here first, then presumably call search_jobs. But there is no explicit when-to-use/when-not or a named alternative, and the phrase 'disclose the source and caps in chat' reads as an instruction to the agent rather than selection guidance.

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