Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

importyeti_search

Search ImportYeti companies and suppliers by name to get kind, slug, country, address, and shipment stats; use a company slug to retrieve detailed company records.

Instructions

Search ImportYeti companies and suppliers by name. Searches ImportYeti for companies and suppliers matching a name, returning each match's kind (company or supplier), slug, country, address, and headline shipment stats. A "company" result's slug chains into GET /importyeti/company.

Input Schema

NameRequiredDescriptionDefault
qYesCompany or supplier name to search for
pageNo1-indexed result page, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does disclose the return shape (kind, slug, country, address, headline shipment stats) plus the follow-up call. It does not mention pagination semantics or any rate/permission constraints, but for a read-only name search this is largely compensated.

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?

Front-loaded with the core action and kept to three sentences. The second sentence restates the first ('Search... by name' / 'Searches... matching a name'), which is minor redundancy, but nothing important is buried.

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?

No output schema or annotations exist, so the description does the work of describing returned fields and the next-step call, which is sufficient for a two-parameter search tool. Only pagination behavior is left unspecified.

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 both parameters (q, page) are fully documented in the schema. The description adds no format or syntax detail beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb (search) and resource (ImportYeti companies and suppliers by name) and explicitly scopes results to company/supplier. The final sentence differentiates it from the sibling importyeti_company by explaining the slug chaining relationship, so an agent can route correctly without opening either schema.

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?

The chaining note ('A company result's slug chains into GET /importyeti/company') implies the workflow but never explicitly states when to use this vs. the detail sibling, and gives no exclusions or prerequisites. Usage is inferable but not spelled out.

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

Deploy Server

Other Tools