Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB private-file usage

campus_get_private_files_info
Read-onlyIdempotent

Retrieve private-file counts and storage usage for an authenticated user in a given year without listing or modifying files.

Instructions

Read the authenticated user's private-file counts and storage usage without listing or changing files.

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": {
      "year": "<year>"
    },
    "name": "campus_get_private_files_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: results are aggregate counts rather than a file listing, and the operation is scoped to the caller's own account with no cross-user access.

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?

One sentence, front-loaded with the verb and resource, followed immediately by the scoping constraint and the exclusion clause. Nothing is redundant or padded.

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

Completeness3/5

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

For a single-parameter read-only aggregate tool with no output schema, the description is mostly sufficient: it conveys read-only behavior, personal scope and that no file listing is returned. However, the mandatory 'year' argument is entirely unexplained, which is a meaningful gap for the one input the agent must supply.

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

Parameters2/5

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

The single parameter 'year' has 0% schema description coverage and the description never mentions it. It does not explain whether the value is a calendar or academic year, why the format is YYYY-MM, or whether it bounds the aggregation window — an agent must guess from the regex pattern alone.

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 names a specific verb ('Read') and a specific resource ('private-file counts and storage usage') scoped to 'the authenticated user's'. It also carves out what it does not do ('without listing or changing files'), which separates it from download/file-listing siblings, though it never names an alternative tool.

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 only implied through exclusions: the agent learns not to call it for listing or modifying files, which hints that file-enumeration tools exist elsewhere. There is no explicit statement of when this tool is the right choice or which sibling to use instead for file contents.

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