subfeed_get_entity
Get entity details.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Entity ID |
Subfeed
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- 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 provided, so the description bears full responsibility for behavioral disclosure. It only repeats the basic action and offers no information about return format, error handling, permissions, or read-only guarantees. 'Get' weakly implies a safe read, but this is not explicit.
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?
The description is a single short sentence with no wasted words, making it concise and front-loaded. However, it is so terse that it adds little beyond the tool name, keeping it from a perfect score.
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?
Given the lack of annotations and output schema, the description is too minimal. It doesn't clarify the return shape, prerequisites (e.g., how to obtain an ID), or how this tool differs from list/discover variants. More context is needed for reliable invocation.
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?
The input schema has 100% description coverage for the single id parameter, so the schema already documents it. The description adds no extra semantic nuance about how the ID is used or what entity types are valid.
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 'Get entity details' clearly states the verb (get) and resource (entity), distinguishing it from sibling tools like list_entities and discover_entities. However, 'details' is vague and doesn't specify the exact fields or shape 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 guidance on when to use this tool versus alternatives. It does not mention that list_entities might be needed first to obtain an ID or that discover_entities provides search-like functionality.
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.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a clear, distinct operation: entity CRUD, addon management, discovery, interaction, and registration. While chat, invoke, and webhook all involve communication, their descriptions clearly differentiate entity chat from public invocation and webhook payloads.
Naming Consistency4/5
All tools share the 'subfeed_' prefix and use snake_case, with most following a verb_noun pattern (create_entity, delete_entity, list_addons). A few use bare verbs (chat, invoke, register) or noun-only (webhook), but the pattern is still recognizable and predictable.
Tool Count5/5
15 tools is at the upper edge of the ideal range, but it matches the server's broad scope covering entities, addons, models, discovery, and user registration. Each tool serves a distinct purpose and none feel redundant.
Completeness4/5
The surface covers full entity lifecycle (create, get, update, delete, publish), addon management (enable, disable, list), entity discovery, and user registration. Minor gaps like an explicit unpublish or webhook management can be worked around via update_entity or standalone webhook sending.