Skip to main content
Glama

list_profiles

Retrieve available assistive-technology profiles for scoring. Use the returned profile IDs with analysis tools to evaluate navigation difficulty for specific screen reader and platform combinations.

Instructions

List the assistive-technology (AT) profiles available for scoring. Each profile models a specific screen reader and platform — e.g., NVDA on Windows, VoiceOver on iOS — with its own navigation cost weights and action vocabulary. Returns an array of {id, name, platform, description} for each profile.

Read-only, no parameters, static data. Call once to discover valid profile IDs, then pass a profile ID to analyze_url, trace_path, or analyze_pages. Default profile for all analysis tools is 'generic-mobile-web-sr-v0' if none is specified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_profiles'. Registers the tool on the MCP server. Calls listProfiles() and getProfile() from the profiles module to fetch all registered AT profiles and returns them as a JSON array with id, name, platform, and description.
    export function registerListProfiles(server: McpServer): void {
      server.registerTool(
        "list_profiles",
        {
          description:
            "List the assistive-technology (AT) profiles available for scoring. " +
            "Each profile models a specific screen reader and platform — e.g., NVDA on Windows, " +
            "VoiceOver on iOS — with its own navigation cost weights and action vocabulary. " +
            "Returns an array of {id, name, platform, description} for each profile.\n\n" +
            "Read-only, no parameters, static data. Call once to discover valid profile IDs, " +
            "then pass a profile ID to analyze_url, trace_path, or analyze_pages. " +
            "Default profile for all analysis tools is 'generic-mobile-web-sr-v0' if none is specified.",
          inputSchema: {},
        },
        async () => {
          const profiles = listProfiles();
          const details = profiles.map((id) => {
            const p = getProfile(id);
            return {
              id,
              name: p?.name ?? id,
              platform: p?.platform ?? "unknown",
              description: p?.description ?? "",
            };
          });
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(details, null, 2),
              },
            ],
          };
        },
      );
    }
  • Input schema for the 'list_profiles' tool. Accepts no parameters (inputSchema: {}).
    {
      description:
        "List the assistive-technology (AT) profiles available for scoring. " +
        "Each profile models a specific screen reader and platform — e.g., NVDA on Windows, " +
        "VoiceOver on iOS — with its own navigation cost weights and action vocabulary. " +
        "Returns an array of {id, name, platform, description} for each profile.\n\n" +
        "Read-only, no parameters, static data. Call once to discover valid profile IDs, " +
        "then pass a profile ID to analyze_url, trace_path, or analyze_pages. " +
        "Default profile for all analysis tools is 'generic-mobile-web-sr-v0' if none is specified.",
      inputSchema: {},
    },
  • src/mcp/index.ts:36-36 (registration)
    Registration call that wires registerListProfiles into the MCP server creation.
    registerListProfiles(server);
  • src/mcp/index.ts:13-13 (registration)
    Import of the registerListProfiles function from the tools/list-profiles module.
    import { registerListProfiles } from "./tools/list-profiles.js";
  • The core listProfiles() helper that returns all registered profile IDs from the internal profileRegistry Map.
    export function listProfiles(): string[] {
      return [...profileRegistry.keys()];
    }
Behavior5/5

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

No annotations provided, but the description fully discloses behavior: read-only, no parameters, static data. No contradictions or omissions for this simple tool.

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?

Concise and front-loaded: first sentence states purpose, second provides usage guidance. Every sentence adds necessary detail without redundancy.

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?

The description covers purpose, content, usage pattern, default behavior, and return format. No output schema exists, but the description compensates fully.

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?

No parameters exist, so schema coverage is 100%. The description adds value by detailing the return array structure ({id, name, platform, description}), exceeding the baseline for 0-param tools.

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?

The description clearly states the tool lists assistive-technology profiles and explains what each profile contains (e.g., NVDA on Windows, VoiceOver on iOS). It distinguishes from sibling tools by noting the profile IDs are used in analysis tools like analyze_url.

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?

Explicitly states when to use: call once to discover profile IDs, then pass to analysis tools. Mentions the default profile if none specified, providing clear context and alternatives.

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/tactual-dev/tactual'

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