Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

Find Group

Find_Group
Read-only

Look up a group's information in Files.com using its group ID. Returns group details for user management.

Instructions

Show Group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoGroup ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

The description 'Show Group' adds no behavioral details beyond the annotation's readOnlyHint. It does not disclose what the tool returns, whether it supports lookup by ID only, or any side effects. The minimal description fails to leverage the opportunity to provide additional context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is brief (2 words), it is under-specified rather than concise. It does not earn its place by conveying necessary information; instead, it omits essential details, making it insufficient for an agent to understand the tool's usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single optional parameter and the existence of an output schema, the description should explain that this tool retrieves a group by ID and possibly describe the return format. It fails to provide any contextual completeness, relying solely on the tool name.

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?

The input schema has 1 parameter (id) with 100% schema description coverage ('Group ID.'). The tool description does not add any further meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Show Group' is a tautology of the title 'Find Group' and the tool name 'Find_Group'. It does not specify the action beyond the name itself, offering no clarity on what the tool does or how it differs from other find/list tools.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives like List_Group or Find_User. The description lacks any context about appropriate scenarios, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Files-com/files-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server