Skip to main content
Glama

retrieve_field_plugins

Facilitates retrieval of field plugins across space, org, or partner contexts with customizable filters for user-specific plugins, pagination, and search by name or slug.

Instructions

    Retrieves multiple field plugins (field types) across different contexts.

    Args:
        context (str): 'space', 'org', or 'partner'
        only_mine (int): 1 = only plugins created by authenticated user
        page (int): pagination page number
        per_page (int): plugins per page (max 100)
        search (str): search filter for plugin name or slug
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNospace
only_mineNo
pageNo
per_pageNo
searchNo
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions pagination and search filtering, but doesn't disclose authentication requirements, rate limits, error conditions, or what the return format looks like. For a retrieval tool with 5 parameters, this leaves significant behavioral gaps.

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?

Perfectly structured with a clear purpose statement followed by parameter documentation. Every sentence earns its place - the first establishes what the tool does, the parameter list provides essential usage details without redundancy.

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 retrieval tool with 5 parameters and no annotations or output schema, the description covers parameter semantics well but lacks behavioral context about authentication, response format, or error handling. It's adequate for basic usage but incomplete for robust agent operation.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear explanations for all 5 parameters: context options, meaning of 'only_mine', pagination details, and search functionality. This adds substantial value beyond the bare schema.

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 clearly states the verb ('Retrieves') and resource ('multiple field plugins'), specifying they are 'field types' across different contexts. It distinguishes from sibling 'retrieve_field_plugin' (singular) by emphasizing 'multiple', but doesn't explicitly contrast with other retrieval tools like 'retrieve_all_extensions'.

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?

No guidance on when to use this tool versus alternatives like 'retrieve_field_plugin' (singular) or other retrieval tools. The description mentions contexts ('space', 'org', 'partner') but doesn't explain when each is appropriate or provide any exclusion criteria.

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

Related 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/Kiran1689/storyblok-mcp-server'

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