Skip to main content
Glama

ADV IT Performance (AEO websites)

ADV Knowledge: Triples, FAQ, Topics, Links

get_adv_knowledge
Read-onlyIdempotent

Read-only. Return ADV's semantic triples, buyer FAQ answers, knowsAbout topics and hub/spoke page links, built from the ADV marketing research corpus; prices and credentials come from the fact registry. Optional section: triples, faq, topics, links or all.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paged sections (default 1).
sectionNotriples | faq | topics | facts | links | sources | all (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the description's leading 'Read-only.' adds nothing. It does contribute provenance context ('built from the ADV marketing research corpus; prices and credentials come from the fact registry') and signals that some sections are paged, which is modest but real added value.

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?

Two compact sentences with the resource scope front-loaded, followed by provenance and the optional section hint. The leading 'Read-only.' and the partial re-listing of enum values are mildly redundant with the annotations and schema, but there is little wasted text.

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 two-parameter, read-only retrieval tool with no output schema, the description is largely sufficient: it tells the agent what content comes back and where provenance lies. The gaps are minor — pagination behavior and the fact that 'facts' and 'sources' are valid sections are left to the schema.

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%, so both parameters are already documented with defaults and allowed values, giving a baseline of 3. The description restates the section options but only partially (missing 'facts' and 'sources') and says nothing about the 'page' parameter, so it adds no meaning beyond the schema and is slightly less complete than it.

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?

The description names a specific verb ('Return') and enumerates the exact resources returned: semantic triples, buyer FAQ answers, knowsAbout topics, and hub/spoke page links, down to the corpus they derive from. It does not explicitly contrast with get_offers or query_service_offer, so sibling differentiation is only implicit (the 'prices and credentials come from the fact registry' clause hints that this tool is not the pricing source).

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 implied rather than stated: 'Optional section: triples, faq, topics, links or all' tells the agent the section argument is optional and the default is 'all'. There is no explicit when-to-use vs. when-to-use-another-tool guidance, and the section list omits 'facts' and 'sources', which the schema does allow.

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