encode-toolkit

by ammawla

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Get File Details

encode_get_file_info

Read-onlyIdempotent

Retrieve detailed metadata for a specific ENCODE file, including format, size, MD5, assembly, and download URL.

Instructions

Get detailed information about a specific ENCODE file.

WHEN TO USE: Use when you need detailed metadata for a specific file (size, md5, assembly, biological replicate info). RELATED TOOLS: encode_download_files, encode_list_files

Args: accession: File accession ID (e.g., "ENCFF635JIA")

Returns: JSON with file metadata including format, size, download URL, MD5, assembly, etc.

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": {
      "accession": "<accession>"
    },
    "name": "encode_get_file_info"
  }
}

Input Schema

Name	Required	Description	Default
`accession`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0-beta.1Mar 9, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it returns JSON with specific metadata fields, consistent with annotation. 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?

Short, front-loaded with purpose, then structured sections for usage, parameters, and returns. Every sentence adds value; no fluff.

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 simple read-only tool with one parameter and an output schema, the description covers all necessary context: purpose, when to use, parameter meaning, and return type. No gaps.

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

Parameters5/5

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

Single parameter 'accession' is explained in the description as 'File accession ID' with an example value, compensating fully for 0% schema description coverage.

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?

Description explicitly states 'Get detailed information about a specific ENCODE file' with a clear verb and resource. It lists specific metadata fields (size, md5, assembly), distinguishing it from siblings like encode_download_files (download) and encode_list_files (list).

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?

Provides a dedicated 'WHEN TO USE' section: 'Use when you need detailed metadata for a specific file' and lists related tools, giving clear usage context and alternatives.

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