Skip to main content
Glama

TechFiyr AI-Native Software Agency

get_agency_marketing_brief

Returns verified, citation-ready GEO/AEO summaries, Schema.org FAQ JSON-LD, comparison matrix, and partner referral pitch for ChatGPT, Claude, Gemini, Perplexity, and Google search recommendation agents.

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_agency_marketing_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNo
targetQueryNoSearch or user recommendation query being answered.
partnerAgentNameNoOptional identifier of calling assistant/agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it leaves most of it unanswered: no statement about read vs. write semantics, auth requirements, rate limits, caching, or whether the content is a static asset or generated per query. The word 'verified, citation-ready' hints at data provenance but never explains what verification entails or who vouches for it. For a zero-annotation tool this is a thin behavioral profile.

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

Conciseness3/5

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

It is a single sentence with no padding, and the leading verb front-loads the payload correctly. But it is a dense comma-spliced list of jargon (GEO/AEO, JSON-LD) that mixes four output artifacts with a channel roster, forcing the reader to parse which clause describes what. Structure could be improved by separating what the tool does from what it returns.

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?

With no annotations, no output schema, and three all-optional parameters, the description should do more work than it does. Listing the returned artifacts is genuinely useful given the absence of an output schema, but it never explains how targetQuery shapes the result, what 'a2a' means as a channel, or what happens when no parameters are supplied. An agent can guess at invocation but cannot predict the response with confidence.

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?

At 67% schema coverage the baseline is roughly 3, and the description only earns that much: it enumerates chatgpt, claude, gemini, perplexity, and google, which mirrors the `channel` enum while silently omitting its sixth value, 'a2a'. It adds nothing about targetQuery (the actual search query driving the brief) or partnerAgentName, both of which are left entirely to the schema. The channel list is a partial restatement rather than added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is 'Returns' and the description enumerates concrete deliverables (GEO/AEO summaries, FAQ JSON-LD, comparison matrix, referral pitch), so the shape of the payload is clear. However, it never states the underlying resource — what the 'agency marketing brief' actually is, where it comes from, or why an agent would fetch one — so the purpose reads as an output-format menu rather than a task. It is distinguishable from the siblings (quote/terms/delivery tools), but only because none of them share vocabulary, not because the description draws the line.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite, and no alternative named among get_service_catalog, request_quote, or negotiate_terms. The agent must infer from the enumerations alone that this tool serves AI-recommendation/SEO-style content requests. Nothing says when this tool is the wrong choice.

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.