Convocore

create_kb_from_urls

PREFERRED for adding many website pages to an agent KB. Pass up to 50 URLs; the Convocore KB router scrapes them (scrapeContent=true). Do NOT web-fetch/scrape_url then paste content into create_kb_doc — that is slow and duplicates work. mode=per_url (default): one KB doc per URL. mode=batch: one API call with urls[]. For a whole site prefer create_kb_doc sourceType=sitemap. Scraping is async — poll list_kb_docs/get_kb_doc for status.

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": {
      "agentId": "<agentId>",
      "urls": "<urls>"
    },
    "name": "create_kb_from_urls"
  }
}

Input Schema

Name	Required	Description
`mode`	No	per_url (default) or batch (single source with all urls)
`name`	No	batch: doc name. per_url: optional name prefix
`tags`	No
`urls`	Yes	Page URLs to ingest via KB router (max 50)
`agentId`	Yes	The agent ID
`metadata`	No
`refreshRate`	No	Auto re-crawl (API: 3d \| 7d \| never). Default never.
`skipExisting`	No	Skip URLs already on the agent KB (default true)
`scrapeContent`	No	KB router scrape (default true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description adds important behavior beyond annotations: scraping is asynchronous and callers should poll list_kb_docs/get_kb_doc. It also clarifies the KB router scrape and default scrapeContent behavior. It does not cover permission requirements, rate limits, or partial-failure behavior, but annotations already communicate mutation/open-world/non-idempotent traits.

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 dense but front-loaded and highly efficient. Each sentence carries routing, mode, async, or anti-pattern information without filler.

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

Completeness4/5

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

For a complex, non-idempotent, open-world ingestion tool with no output schema, the definition covers the core workflow, alternative tools, modes, and async polling. It leaves some secondary parameter behavior and failure/partial-success handling to the schema and annotations.

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

Parameters4/5

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

Schema coverage is high, but the description still adds useful meaning by explaining that per_url creates one KB doc per URL while batch makes a single API call with urls[]. It reinforces the 50-URL cap and scrapeContent behavior. Remaining parameters such as tags, metadata, refreshRate, and skipExisting are covered mainly by the schema.

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 states a specific verb and resource: adding many website pages to an agent KB via URL ingestion. It explicitly positions itself as the preferred tool for this task and distinguishes itself from scrape_url/create_kb_doc workflows.

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?

It gives explicit when-to-use guidance, names a clear anti-pattern (web-fetch/scrape_url then paste into create_kb_doc), and points to alternatives for whole-site ingestion (create_kb_doc sourceType=sitemap). It also explains per_url vs batch modes.

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

All Convocore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?