Skip to main content
Glama

Market Brew

Describe an AI Content Dashboard tool

get_content_tool
Read-onlyIdempotent

Use this when the user asks to describe an AI Content Dashboard tool. Returns only data visible to the linked Market Brew account.

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": {
      "tool": "<tool>"
    },
    "name": "get_content_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results are scoped to the linked Market Brew account — but says nothing about what a "description" contains or how large it is, and there is no output schema to fill that gap.

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 short sentences with the usage trigger front-loaded and no filler. Nothing is wasted, though the brevity comes partly at the cost of missing content rather than through efficient compression.

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 output schema, the description carries full responsibility for explaining the return value, and it only offers an access-scope caveat. It leaves the sole enum parameter unexplained and gives no sense of what a returned "description" looks like, which is inadequate for a tool with 25 selectable modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single `tool` parameter with a 25-value enum is never mentioned in the description. The enum values are somewhat self-descriptive, but nothing explains what selecting one does — whether it picks which dashboard widget to describe, or which analysis engine is applied.

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+resource ("describe an AI Content Dashboard tool") is stated, but it nearly restates the title verbatim and "describe" is vague — it does not say whether this returns a tool's metadata, a configuration summary, or computed dashboard content. It also gives no differentiation from siblings such as analyze_ai_mode or analyze_content_depth, which plausibly return overlapping information.

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?

There is an explicit trigger ("Use this when the user asks to describe an AI Content Dashboard tool"), which is more than nothing. However, there are no when-not conditions and no named alternative for the closely related analyze_* siblings, so the agent must guess whether to describe or analyze.

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