Skip to main content
Glama

at_knowledge_add

Add or update an AT command in the knowledge base, storing it under a specific chipset platform. Supports placeholders, response patterns, and parameter definitions.

Instructions

Add or update an AT command in the knowledge base. Stores in the specified chipset file (e.g. asr, quectel) or _custom. Use at_knowledge_chipsets to see available platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesYAML slug/key, e.g. 'at+csq', 'at+qcell'. Must be unique.
nameNoShort name, e.g. 'Signal Quality'.
typeNoCommand type: empty=AT command, urc=passive URC wait, data=transparent data send.
retryNoRetry count. Default 1.
expectNoExpected response patterns. Example: ['+CSQ:', 'OK'].
paramsNoParameter list. Each param has name/type/default/required.
chipsetNoTarget chipset platform. See at_knowledge_chipsets for options. Default '_custom' (user scratchpad). Common: asr, quectel.
commandYesActual AT command string. Example: 'AT+CSQ', 'AT+QCELL?'. Supports {param} placeholders.
timeoutNoTimeout in seconds. Default 1.0.
standardNoSource: 3gpp / vendor / custom. Default vendor.
descriptionNoFunction description including return value meanings. Multi-line supported.
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'Add or update' but does not clarify idempotency, error handling, authorization needs, or what happens on duplicate keys. This is insufficient for a mutation tool.

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 two sentences with no wasted words. The main purpose is front-loaded, and the reference to at_knowledge_chipsets is placed appropriately.

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?

Despite 11 parameters and no output schema, the description lacks essential context about return values, error conditions, or the add-vs-update behavior. The tool is complex, and the description does not provide a complete picture for effective use.

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%, so all parameters have descriptions in the schema. The description adds minimal extra meaning (e.g., chipset context). Baseline 3 is appropriate as it does not significantly enhance understanding beyond the schema.

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 verb 'Add or update' and the resource 'AT command in the knowledge base', along with storage location (chipset file or _custom). It distinguishes from sibling tools like at_knowledge_list or at_knowledge_search.

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 directs users to at_knowledge_chipsets for available platforms, providing helpful context for usage. However, it does not explicitly state when not to use this tool or how it compares to alternatives like at_knowledge_stats or at_send_command.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeng-andrew/at_bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server