Skip to main content
Glama

AceRound AI Interview Copilot

upload_knowledge_base_file

Create an interview knowledge base from a file: its text becomes the knowledge base text; returns the new ID and text length. Pass the file content as base64. Supported: .pdf .doc .docx .txt .md .jpg .jpeg .png .webp, up to 10MB. (Requires the user's sign-in with scope interviews:write.)

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": {
      "fileName": "<fileName>",
      "fileBase64": "<fileBase64>"
    },
    "name": "upload_knowledge_base_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNameYesFile name with extension
fileBase64YesFile content as base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond them: it discloses the return payload (new ID and text length), the 10MB size ceiling, the accepted file types, and the required auth scope interviews:write.

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?

Dense and front-loaded: the core action and return value come first, followed by format and auth constraints. Every sentence carries information, though the parenthetical auth note is slightly tacked on.

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 upload tool with no output schema, the description covers the action, the return values, encoding, accepted formats, size limit, and required scope. An agent has everything needed to call it correctly.

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 100%, so the baseline is 3. The description goes further by explaining that fileBase64 must be base64-encoded file content and by constraining fileName to the listed extensions and 10MB limit, adding meaning the schema alone does not convey.

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?

States a specific verb and resource ('Create an interview knowledge base from a file') and clarifies the input modality (file content as base64), which distinguishes it from the sibling create_knowledge_base. It does not explicitly name or contrast with that sibling, so it stops short of a 5.

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 'from a file' and the supported-extension list, which tells the agent this is the file-based path. However, there is no explicit when-to-use versus create_knowledge_base or add_knowledge_base_entry, and no stated exclusions.

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