Skip to main content
Glama
Sign In
AuditSocials Glossary MCP

AuditSocials Glossary MCP

Official
by auditsocials
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

glossary_search

Find advertising and platform-policy terms by keyword or category. Returns matching terms with short definitions to help you discover terms before requesting detailed explanations.

Instructions

Search the AuditSocials Compliance Glossary by keyword and/or category. Returns matching terms with their short definitions. Use this to discover terms before calling glossary_define.

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": "glossary_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesKeyword to match against term names and definitions
categoryNoOptional category filter: Platform Policy, Legal & Regulatory, Ad Tech & Metrics, Content & Creative, Privacy & Data, Industry-Specific, Enforcement & Risk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It states that the tool returns 'matching terms with their short definitions,' indicating a read-only search. It does not mention potential errors, pagination, or authentication needs, but for a simple search tool this is adequate.

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 extremely concise with two sentences: the first clearly states the action and result, the second provides usage guidance. Every word adds value with no redundancy or filler.

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?

For a search tool with 3 well-documented parameters and an implied list return, the description adequately covers the basics. It explains the output and provides workflow context. It could briefly mention that results are a list of terms, but given the schema covers parameters, this is not a significant gap.

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% with all parameters already described in the schema. The description mentions 'keyword and/or category' but adds no new semantic details beyond what the schema provides, so a baseline score of 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's function: searching the glossary by keyword and/or category and returning matching terms with definitions. It distinguishes itself from the sibling 'glossary_define' by noting this tool is for discovery before calling the define tool.

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 explicitly tells when to use this tool: 'Use this to discover terms before calling glossary_define.' This provides clear guidance on the workflow, though it does not discuss when not to use it or mention the other sibling 'glossary_list_categories'.

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