UseMyContext.ai

Open a file

get_file

Read-only

Get the full text content of one file by id (large files are truncated; use ask_docs for targeted passages). An image returns the picture itself (plus any text read from it at upload); other binary files return a short-lived download link instead. Audited.

Input Schema

TableJSON Schema

Name	Required	Description
`fileId`	Yes	The id of the file to fetch.
`handle`	No	Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.
`projectId`	No	Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`content`	No	The file's extracted text. For an image, the text read from it at upload (approximate; the picture itself rides as an image block). Absent for a binary file or an image with no text.
`truncated`	No	True when the text was truncated at the size guard.
`contentType`	Yes
`downloadUrl`	No	A short-lived download link (valid about 5 minutes).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / properties / content / description

Previous value: -"The file's extracted text. Absent for a binary or image file."New value: +"The file's extracted text. For an image, the text read from it at upload (approximate; the picture itself rides as an image block). Absent for a binary file or an image with no text."

Changed1 schema field changedJul 26, 2026

addedInput schema / properties / handle

Added value: +{
+  "description": "Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.",
+  "type": "string"
+}

Changed1 schema field changedJul 24, 2026

addedInput schema / properties / projectId

Added value: +{
+  "description": "Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.",
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint true and destructiveHint false, but the description adds significant behavioral detail: truncation of large files, image return behavior, download links for binary files, and the 'Audited' note. No contradictions with annotations.

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?

The description is fairly concise (two sentences) with key behavioral caveats front-loaded (truncation and alternative tool). The parameter semantics are handled in the schema, so no redundancy. A minor improvement could be to explicitly state the return format, but overall efficient.

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?

Given the output schema exists, the description doesn't need to detail return values. It covers file type behaviors and alternative tools. However, it does not mention pagination or response size limits beyond truncation, which might be relevant for very large files. Still, it is largely complete for a fetch operation.

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 covers all three parameters thoroughly (fileId, handle, projectId) with detailed semantics. The description does not add much beyond the schema, but the schema is complete, so baseline 3 is appropriate.

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?

The description clearly states it gets the full text content of a file by id, with distinct behavior based on file type. It distinguishes from ask_docs for targeted passages, but does not explicitly compare to list_files or search_files, so it's clear but could differentiate more among siblings.

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

Usage Guidelines4/5

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

Explicitly says to use ask_docs for targeted passages in large files, and mentions shared_context for reading context shared by others. However, it does not mention when to use search_files or list_files as alternatives for finding files, so guidance is present but not exhaustive.

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

All UseMyContext.ai tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.