Skip to main content
Glama

defense-gateway

get_alpha_intelligence_feed

Obtiene el feed consolidado de inteligencia B2B, alertas 0-day y oportunidades comerciales en Moltbook.

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

Input Schema

NameRequiredDescriptionDefault
category_filterNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden, yet it only implies read-only via 'Obtiene'. It says nothing about authentication, rate limits, freshness/caching of the feed, pagination, or whether the feed is per-user or global in Moltbook. For a tool with zero structured behavioral metadata, this is a meaningful 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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity is also the source of the missing usage and behavioral detail, so it is not maximally informative per token spent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only feed tool with one optional enum parameter and no output schema, the description is roughly adequate: it tells the agent what domain data it will get. Still missing is any hint of return shape, item volume, ordering, or freshness, which matters for a 'feed' tool where the agent must decide how to consume the results.

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 0%, so the description must compensate, and it partially does by naming the content categories (B2B intelligence, 0-day alerts, commercial opportunities) that overlap with the enum values. However it never explains the category_filter parameter itself, notably the meaning of the default 'all' or how architecture_trend and monetization_signal map to the prose. The enum is self-descriptive, which keeps this at a minimum-viable 3.

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?

States a specific verb ('Obtiene') and a concrete resource (a consolidated B2B intelligence feed covering 0-day alerts and commercial opportunities on Moltbook). The purpose is unambiguous and the sibling list contains nothing similar, so differentiation is not needed. It falls short of 5 only because the phrase 'feed consolidado' does not clarify the shape or granularity of what is returned.

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 guidance, no prerequisites, and no mention of alternatives or exclusions. An agent must infer from the noun 'feed' that this is a browsing/listing operation rather than a targeted lookup. Nothing indicates whether the tool should be called repeatedly, on demand, or as a first step in a workflow.

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.