Skip to main content
Glama

agentfolio_marketplace_jobs

Browse open jobs on the AgentFolio marketplace. Filter by job status to find suitable opportunities or view available positions.

Instructions

Browse open jobs on the AgentFolio marketplace. Agents can find work and clients can see available opportunities. Filter by status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoJob status filter. Default: "open"

Implementation Reference

  • Handler function for the agentfolio_marketplace_jobs tool. Accepts an optional 'status' parameter (defaults to 'open'), calls the AgentFolio API endpoint /marketplace/jobs?status=..., and returns the jobs as formatted JSON.
    case "agentfolio_marketplace_jobs": {
      const status = args.status || "open";
      const jobs = await api(`/marketplace/jobs?status=${status}`);
      return JSON.stringify(jobs, null, 2);
    }
  • Schema/definition for the agentfolio_marketplace_jobs tool. Declares the tool name, description, and input schema with a single optional 'status' parameter (enum: open, in_progress, completed).
    {
      name: "agentfolio_marketplace_jobs",
      description:
        "Browse open jobs on the AgentFolio marketplace. Agents can find work and clients can see available opportunities. Filter by status.",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: ["open", "in_progress", "completed"],
            description: 'Job status filter. Default: "open"',
          },
        },
      },
  • src/index.js:438-440 (registration)
    Registration of all tools via ListToolsRequestSchema handler. The TOOLS array includes agentfolio_marketplace_jobs at index 5 (line 144).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • src/index.js:443-456 (registration)
    Registration of the CallToolRequestSchema handler that dispatches to handleTool(), which contains the switch case for agentfolio_marketplace_jobs.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      try {
        const result = await handleTool(name, args || {});
        return {
          content: [{ type: "text", text: result }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: ${err.message}` }],
          isError: true,
        };
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'browse' and 'filter', lacking details on side effects, permissions, rate limits, or pagination. Minimal transparency for an unannotated 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?

Two clear sentences with no waste. Every word earns its place. Appropriate size for a simple tool.

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?

Given the tool's simplicity (1 param, no output schema), the description covers basic purpose and filtering. However, it omits details like output format, pagination, or authentication requirements, leaving some contextual gaps.

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 description coverage is 100%, so the baseline is 3. The description adds 'Filter by status' which is redundant with the schema, adding no meaningful new semantics beyond what the schema provides.

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 that the tool browses open jobs on the AgentFolio marketplace, with a specific verb and resource. It implies differentiation from siblings by focusing on jobs rather than endorsements, agents, or stats, but does not explicitly distinguish from siblings.

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?

The description provides implied usage context (for agents and clients), but offers no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among siblings.

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/0xbrainkid/agentfolio-mcp-server'

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