FavCRM

This connector has been deprecated

This connector has been replaced by https://glama.ai/mcp/connectors/io.favcrm/favcrm/admin

get_knowledge_document

Read-onlyIdempotent

Fetch a single knowledge document with metadata + extraction/review status. Reviewed content is served via GET /v6/merchant/ai/knowledge/{id}/content; raw/extracted variants are for audit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`documentId`	Yes	Knowledge document ID

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds value by specifying that the response includes metadata and status, and that different content variants are accessed via separate endpoints, providing behavioral context beyond the annotations.

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

Conciseness5/5

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

The description is extremely concise with two sentences. The first sentence states the primary purpose, and the second provides important usage guidance. No unnecessary words or repetition.

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

Completeness5/5

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

Given the simple single-parameter input schema and the existence of an output schema, the description sufficiently covers the tool's functionality. It mentions the response includes metadata and status, and directs to another endpoint for content, making it complete for the agent.

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 description does not add meaning beyond the schema's parameter description. Since schema description coverage is 100%, the baseline is 3, and the description does not provide additional semantics for the documentId parameter.

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?

The description clearly states the verb 'fetch' and the resource 'single knowledge document', and specifies that it includes metadata and extraction/review status. It also distinguishes from sibling tools like list_knowledge_documents by emphasizing 'single' document retrieval.

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

Usage Guidelines5/5

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

The description explicitly informs that reviewed content is served via a different endpoint, and raw/extracted variants are for audit. This provides clear guidance on when to use this tool versus alternative endpoints for content retrieval.

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

All FavCRM tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions that minimize ambiguity. Even related tools like create_post vs create_post_type are well-separated by their targets.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_account, list_services, update_post), with no mixing of naming conventions. The pattern is predictable throughout the set.

Tool Count1/5

190 tools is excessively large for any server, far exceeding the typical 3-15 tool range. The sheer volume overwhelms agents and suggests poor scoping, even for a comprehensive CRM platform.

Completeness4/5

The tool set covers CRUD operations across many domains (CRM, bookings, marketing, CMS, etc.), but notable gaps exist (e.g., no delete_account, delete_contact, update_booking). These are minor given the vast surface.

Resources

Need Help?