Skip to main content
Glama
Sign In

JobMojito

by com.jobmojito
OverviewDiscussionsAdmin

List knowledge base stores

list_knowledge_base_stores
Read-onlyIdempotent

[Knowledge base] The company's knowledge base stores with their document counts: the knowledge_base_store_id create_interview draws on and upload_knowledge_base_document adds to. strict=true means the AI uses only these documents.

Every argument in full, with examples: get_tool_reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_knowledge_base_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
llm_modelNoYour model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
merchant_idNoOptional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
dataYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds genuinely new context by saying each store carries a document count and that strict=true restricts the AI to those documents only. It omits pagination, ordering and auth behavior, but that is a modest gap given the annotation coverage.

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?

Two compact sentences lead with the resource and its payload, and a third sentence routes the agent to get_tool_reference. Nothing is redundant, though the reference sentence could be trimmed to a clause.

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 simple read-only list tool with an output schema and fully described parameters, the description covers purpose, returned payload and cross-tool relevance. Missing only explicit guidance on when not to use it and on scoping behavior.

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%, so llm_model, merchant_id and conversation_id are already fully documented in the schema and need no restating. The description adds no parameter-level meaning, and 'strict=true' refers to a returned store attribute rather than an input argument; the pointer to get_tool_reference for full argument examples is only marginal help.

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 resource (the company's knowledge base stores) plus what it returns (document counts), and ties the store id to the sibling tools that consume it (create_interview, upload_knowledge_base_document). An agent can distinguish it from list_knowledge_base_documents without opening either schema.

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?

The connection to create_interview and upload_knowledge_base_document implies when an agent would want a store id, but there is no explicit 'use this when / use X instead' statement or exclusion relative to list_knowledge_base_documents. Usage is inferable rather than stated.

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

All JobMojito toolsInspect
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