Skip to main content
Glama
Sign In
AT Bridge

AT Bridge

by zeng-andrew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

at_knowledge_search

Search an AT command knowledge base by keyword and filter by standard, vendor, or custom sources to find relevant commands.

Instructions

Search the AT command knowledge base. Supports filtering by keyword (key/name/description/AT string) and source (3gpp/vendor/custom).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "at_knowledge_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTag filter (matches any tag). Example: ['urc', 'quectel'].
queryNoSearch keyword. Searches key, name, description, AT string. Examples: 'signal', 'tcp', 'CGMI'. Empty returns all commands.
standardNoFilter by source: 3gpp (standard), vendor (vendor-specific), custom (user-defined).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the search filters by keyword and source but does not detail response format, pagination, limits, or error behavior. Adequate but not thorough.

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

Conciseness5/5

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

The description is a single sentence with parenthetical details—concise and front-loaded with the main action. No extraneous words.

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

Completeness3/5

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

Given 3 optional parameters, no output schema, and no annotations, the description covers core behavior but lacks details on output format, ordering, or error handling. Complete for basic use but could be more comprehensive.

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 description coverage is 100%. The description adds a summary of filtering dimensions (keyword searches key/name/description/AT string; source types) but doesn't add significant meaning beyond the schema. 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?

The description clearly states the tool searches the AT command knowledge base, specifying the resource and verb. It also mentions filtering by keyword and source, distinguishing it from sibling tools like at_knowledge_list or at_knowledge_add.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool (search with filters) and includes a note that empty query returns all commands. However, it does not explicitly state when not to use it or compare with alternatives like at_knowledge_list.

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