Skip to main content
Glama

add_source

Import a local Markdown, text, PDF, or HTML file by absolute path and ingest it into the project wiki so agents can search and cite the source.

Instructions

Import a local file (Markdown, text, PDF, HTML) into the project and ingest it into the wiki.

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": {
      "path": "<path>"
    },
    "name": "add_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of the file
ingestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden. It hints at a mutation ('ingest it into the wiki') but discloses nothing about side effects: whether a duplicate source is created on re-import, whether existing pages are overwritten, whether ingestion is synchronous or eventually consistent, or what errors look like for unsupported/corrupt files.

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?

A single front-loaded sentence with zero filler: verb, resource, and accepted formats in order of importance. Nothing to trim.

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?

For a mutating ingestion tool with no annotations and no output schema, the description leaves key gaps: the ingest flag is never mentioned, no return/result expectations are set, and duplicate/overwrite behavior is unknown. An agent could call it, but cannot predict the consequences.

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 50%: 'path' is documented in the schema, and the description usefully adds the accepted file formats for that parameter. But the 'ingest' boolean (default true) is undocumented in both schema and description, and the text implies ingestion always happens, leaving the opt-out invisible. Mixed value nets out around baseline.

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?

Names a specific verb (import/ingest) and resource (local file into the project/wiki), and enumerates the supported formats (Markdown, text, PDF, HTML). This clearly separates it from the read-oriented siblings (list_pages, read_page, search_wiki), though it does not explicitly say so.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'Import' – an agent can infer this is the way to get local content into the wiki. However, there is no statement of prerequisites (does the path need to be readable by the server? relative paths rejected?), no when-not-to-use, and no mention that this is the sole ingestion path among otherwise read-only siblings.

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