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). Binary files (images etc.) 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. Absent for a binary or image file.
`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. Dates show when Glama detected each change.

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.7/5.0

Behavior5/5

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

Discloses truncation for large files, download links for binary files, and auditing. Adds meaningful context beyond annotations (readOnlyHint, destructiveHint), with no contradictions.

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?

Two sentences, front-loaded with core purpose, no wasted words. Each sentence adds distinct value.

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?

Covers return types, truncation, binary file handling, and auditing. Given output schema exists and annotations are rich, description is fully complete for this tool.

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 coverage is 100%, so description does not need to add much. It only briefly mentions fileId usage without additional syntax or format details. Adequate but not enriching.

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?

Clearly states the tool gets full text content of a file by ID, distinguishes from sibling 'ask_docs' for targeted passages. Also specifies behavior for binary files and audits.

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?

Explicitly tells when to use (get full content) vs ask_docs (targeted passages), notes truncation for large files, and mentions auditing. Provides clear context for alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Most tools have clear boundaries, but fetch/get_file and search/search_files are explicit aliases of each other, creating redundant purposes. account vs info and list_files vs search_files also require careful reading to tell apart, though the descriptions do provide guidance.

Naming Consistency3/5

The set mixes verb_noun names (list_files, query_table, suggest_update) with standalone nouns (account, info, profile) and bare verbs (fetch, search). The naming is readable and lowercase throughout, but the conventions are not uniform.

Tool Count5/5

Thirteen tools is a reasonable, well-scoped number for a personal-context and document-access server. The two alias pairs add some redundancy but do not make the set feel bloated.

Completeness4/5

The server covers the core read-only workflows: discovering files, searching semantically, querying tabular data, retrieving full documents, reading profiles, and accessing shared context. Direct profile editing or file mutations are intentionally out of scope for this read-only connection, and suggest_update provides the one sanctioned write path.

Open a file

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources