Skip to main content
Glama
Sign In
FeathersMCP

FeathersMCP

by feathersjs-ecosystem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-community-post

Retrieve a community contribution's full content using its ID from search-community results, so you can read complete posts beyond search snippets.

Instructions

Fetch the full content of a community contribution by id (from search-community results).

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": {
      "id": "<id>"
    },
    "name": "get-community-post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe community post ID from search-community results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.16

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't indicate whether the fetch is read-only (though 'Fetch' implies read), whether it returns error handling for missing IDs, rate limits, or format of the returned content. Minimal behavioral context.

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?

Single, efficient sentence that front-loads the action and resource. No unnecessary words, though could be slightly more explicit about the return value.

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 simple one-parameter fetch tool, the description covers the essential purpose. However, with no annotations and no output schema, additional context such as response shape, error behavior, or authentication requirement would improve completeness.

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% and the single parameter's schema description already states it's the ID from search-community results. The description merely repeats 'by id' without adding format or other constraints. Baseline 3 per guidelines.

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

Purpose5/5

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

States a specific verb (Fetch), resource (full content of a community contribution), and key modifier (by id). Distinguished from sibling search-community which is referenced as the source of the ID.

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

Usage Guidelines4/5

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

Implied usage: after searching via search-community, use this tool to retrieve the full post. However, it doesn't explicitly state when NOT to use this tool or contrast with get-doc/get-menu/get-schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools