Skip to main content
Glama

Search Knowasiak

search
Read-onlyIdempotent

Search Knowasiak, a public network of 14,000+ businesses and business owners, for businesses, people and posts, or (type "help") its help guides on how the site works. Returns ids to read in full with fetch, with a short snippet and the public URL of each.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhat to return. Default: all (profiles and posts).
limitNoHow many results. Default: 10.
queryYesWhat to look for, e.g. "packaging design Sydney" or "ISO 9001 composites manufacturer". For help: "how does the feed rank posts".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What to look for, e.g. \"packaging design Sydney\" or \"ISO 9001 composites manufacturer\"."New value: +"What to look for, e.g. \"packaging design Sydney\" or \"ISO 9001 composites manufacturer\". For help: \"how does the feed rank posts\"."
    • changedInput schema / properties / type / description
      Previous value: -"What to return. Default: all."New value: +"What to return. Default: all (profiles and posts)."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "all",
      -  "businesses",
      -  "people",
      -  "posts"
      -]New value: +[
      +  "all",
      +  "businesses",
      +  "people",
      +  "posts",
      +  "help"
      +]
  2. First observed

TDQS

A3.7/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, so the safety profile is covered. The description adds genuinely useful context beyond that: the public nature and size of the corpus, and that each result carries an id, a short snippet, and a public URL. It omits pagination behavior and rate limits, which keeps it from a 5.

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?

A single front-loaded sentence that leads with the verb and corpus before the return details; every clause contributes. The nested parenthetical about "help" is slightly awkward but does not waste space.

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?

With no output schema and only three fully documented parameters, the description fills the main gap by explaining what is returned (ids, snippets, public URLs) and pointing to fetch for follow-up. Only pagination and result-volume behavior are left unaddressed.

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%, including enum values, defaults, and example queries, so the schema already does the heavy lifting and a 3 is the baseline. The description only reinforces the "help" mode and the snippet/URL return shape, adding little parameter-level meaning beyond what is structured.

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 (Search) and enumerates the resource set (businesses, people, posts, help guides) plus the corpus size, so an agent knows exactly what it queries. It does not differentiate itself from siblings such as find_businesses, discover_people, or latest_posts, so it falls short of a 5.

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: something like 'use this for broad discovery across entity types.' The one piece of real routing guidance is the handoff to fetch for full records, and the parenthetical hint that typing "help" retrieves site documentation. There is no statement of when to prefer this over the specialized sibling tools.

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