Skip to main content
Glama
jtkehler

crowdsmart-mcp

by jtkehler

create_knowledge_agent

Creates a private Knowledge Agent you own, starting with no documents; add documents later and share it or include it in Jams for focused Q&A and multi-agent discussions.

Instructions

Create a Knowledge Agent that you own. It is private and has no documents yet.

Add documents with upload_document or add_text_document. To let others ask the agent, share it with set_knowledge_agent_visibility. To have several agents discuss a topic, give each one its own perspective (expertise_headline and system_prompt) and its own documents, then put them in a Jam with create_jam. Your agents do not need to be shared to take part in your Jam.

Args: name: The agent's name. expertise_headline: One line on what the agent knows, shown on its card. system_prompt: How the agent describes itself and its focus. It does not need to tell the agent to keep to its documents: it does that already. mode: Default way of answering. "generative" writes answers that cite passages. "referenced" returns the passages word for word. allow_foundation_backfill: Let the agent answer from the model's general knowledge when its documents cannot. Such answers are labeled. community_id: Home community, from list_my_communities. Default: your default community.

Input Schema

NameRequiredDescriptionDefault
modeNogenerative
nameYes
community_idNo
system_promptNo
expertise_headlineYes
allow_foundation_backfillNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real context — the new agent is private by default and empty, the system prompt need not instruct document restriction because that is enforced already, and backfill answers are labeled. It doesn't cover rate limits or duplicate-name behavior, so not a 5.

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?

Front-loaded with purpose, then workflow, then a clean Args block. Slightly long, but nearly every sentence carries distinct information; the only marginal item is the Jam orchestration paragraph, which is useful but could be trimmed.

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?

For a 6-parameter creation tool with an output schema present (so return values need not be described), the description covers purpose, default state, parameter semantics, and the surrounding workflow. An agent has everything needed to call it correctly on the first attempt.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: it explains all six parameters, including the two enum values of mode ('generative' cites passages vs 'referenced' returns them verbatim), the source of community_id (list_my_communities), and the labeling behavior of allow_foundation_backfill. This is meaningfully more than the schema conveys.

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 and resource ('Create a Knowledge Agent that you own') and immediately gives the resulting state ('private, no documents yet'). This distinguishes it cleanly from update_knowledge_agent, set_knowledge_agent_visibility and list_knowledge_agents among the siblings.

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?

Explicitly routes the agent to the follow-on tools: upload_document/add_text_document to populate, set_knowledge_agent_visibility to share, create_jam to orchestrate multi-agent discussion, plus the note that sharing is not required for Jam participation. This is exactly the when-and-what-next guidance most definitions lack.

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