Skip to main content
Glama

Re-read a knowledge document from its link

dosai_refresh_knowledge_document
Destructive

For a document that was added by a link to a web page (file_type url in dosai_list_knowledge): open the page again and replace the document's text with what is there now. If the page cannot be read or indexing fails, the previous text stays and the bot keeps answering from it. Re-reading is charged to the project balance like adding a document. Documents added as text or as a file are changed with dosai_update_knowledge_document. Requires editor role.

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": {
      "project_id": "<project_id>",
      "document_id": "<document_id>"
    },
    "name": "dosai_refresh_knowledge_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
document_idYesFrom dosai_list_knowledge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / document_id / description
      Previous value: -"Knowledge base document id, as returned by dosai_list_knowledge."New value: +"From dosai_list_knowledge."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  3. Changed2 schema fields changed
    • removedInput schema / properties / document_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag a destructive, open-world, non-read-only operation, but the description adds context annotations cannot express: on failure the previous text is retained and the bot keeps answering from it, the re-read consumes project balance like adding a document, and an editor role is required. Failure semantics, billing impact and auth requirements are exactly the traits an agent needs before invoking a destructive refresh.

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?

Four compact sentences, each carrying distinct load: eligibility condition first, then the action, then failure and cost behavior, then the sibling alternative and role requirement. No restatement of the title or schema and no filler.

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 two-parameter destructive refresh with no output schema, the definition covers eligibility, effect, failure handling, cost, authorization and the alternative tool. There is no evident gap an agent would need to resolve before calling it.

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 both parameters already point to their lookup tools (dosai_list_projects, dosai_list_knowledge). The description reinforces the document_id source implicitly through the file_type reference but adds no new meaning about format or constraints, so the baseline of 3 applies.

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 ('open the page again and replace the document's text with what is there now') plus a hard scope constraint (only documents added by link, file_type url). This clearly separates it from dosai_update_knowledge_document, which the description explicitly assigns to text/file documents.

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?

Gives both the when and the when-not: use it for link-based documents, and use dosai_update_knowledge_document for documents added as text or as a file. It also names dosai_list_knowledge as the place to confirm the document type, so the agent can verify the precondition before calling.

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.

Resources