Skip to main content
Glama

openart_get_character

Read-only

Retrieve detailed information about a character from OpenArt using its unique ID.

Instructions

Get details for a specific OpenArt character by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCharacter ID

Implementation Reference

  • The getCharacter function is the handler for openart_get_character. It navigates to the character page on OpenArt, scrapes name, background story, and voice from the DOM, and returns the character details.
    export async function getCharacter(id: string): Promise<Character & { background_story?: string; voice?: string }> {
      const page = await newPage();
      try {
        await page.goto(`${BASE_URL}/character/${id}`);
        await page.waitForLoadState("networkidle");
    
        // TODO: replace selectors
        const name = (await page.locator("h1").textContent())?.trim() || "";
        const story = (await page.locator('[data-background-story]').textContent())?.trim();
        const voice = (await page.locator('[data-voice]').textContent())?.trim();
    
        return {
          id,
          name,
          url: `${BASE_URL}/character/${id}`,
          background_story: story,
          voice,
        };
      } finally {
        await page.close();
      }
    }
  • src/index.ts:30-39 (registration)
    Tool registration in the tools array with its name, description, inputSchema (requiring an 'id' string parameter), and annotations.
    {
      name: "openart_get_character",
      description: "Get details for a specific OpenArt character by ID.",
      inputSchema: {
        type: "object",
        properties: { id: { type: "string", description: "Character ID" } },
        required: ["id"],
      },
      annotations: { readOnlyHint: true, openWorldHint: true },
    },
  • src/index.ts:93-95 (registration)
    Request handler switch-case that routes 'openart_get_character' calls to the getCharacter function, parsing the 'id' argument with Zod.
    case "openart_get_character":
      result = await getCharacter(z.object({ id: z.string() }).parse(args).id);
      break;
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Get details' aligns but adds no extra behavioral context (e.g., rate limits, auth). No contradiction.

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 of 10 words with no redundant information, perfectly concise and front-loaded.

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

Completeness4/5

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

Given the simple single-parameter tool, read-only nature, and no output schema, the description is largely complete. Could mention what details are returned (e.g., stats, properties) but not essential.

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?

Schema coverage is 100% with one parameter 'id' described as 'Character ID'. Description does not elaborate further (e.g., format, source), so it meets baseline but adds no extra value.

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 uses a specific verb ('Get details') and resource ('specific OpenArt character') with method ('by ID'), clearly distinguishing it from siblings like create, list, or generate.

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?

Implies usage when you need details of a known character by ID, but does not explicitly state when to use vs alternatives like list_characters or create_character. No exclusions or prerequisites provided.

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/jbertus/openart-mcp'

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