Skip to main content
Glama

Little Works

list_portfolio

Public portfolio / featured creations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers very little. 'Public' weakly implies no authentication and read-only access to publicly visible data, but nothing is said about ordering, pagination, result size, or whether the two concepts (portfolio vs. featured creations) are merged into one response.

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

Conciseness3/5

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

It is only a single fragment, so nothing is wasted, but the brevity comes from under-specification rather than disciplined editing. There is no front-loaded verb or scope statement for an agent to anchor on.

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

Completeness2/5

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

The tool is simple (no params, no output schema, no annotations), yet the description still omits what an agent most needs: what the returned entries look like and how this differs from the many other list_* tools. A single clarifying sentence about the returned content would have made it complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The empty schema is fully consistent with a parameterless list operation.

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

Purpose2/5

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

The description is a noun fragment, 'Public portfolio / featured creations.', with no verb and no clear statement of what the tool does with that resource (list it? return it? filter it?). It largely restates the name 'list_portfolio' with an alternative gloss, and the slash-joined phrasing leaves it ambiguous whether the tool returns portfolio items, featured creations, or both.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to alternatives, despite many overlapping list_* siblings such as list_projects, list_materials, and list_info_pages. The word 'Public' hints at scope but does not tell an agent when this tool is the right choice over those siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources