Skip to main content
Glama

Attach job photo in CrewNest

crewnest_attach_job_photo
Read-onlyIdempotent

Attach job photo in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

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": "crewnest_attach_job_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description is consistent with them while adding genuinely new context: the return value is step-by-step UI instructions and the call mutates nothing. This is exactly the kind of clarification that matters when the name suggests a write action. It still does not explain how the target job or photo is identified given zero parameters, nor whether the browser session must already be authenticated.

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

Conciseness2/5

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

The core two sentences are front-loaded and useful, but the final sentence about CrewNest's official Job Pricing MCP server and its three read-only tools is entirely off-topic for this tool and reads as promotion. Phrases like 'from ChatGPT, Claude or any AI agent' add length without adding selection value. Roughly a third of the description does not earn its place.

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?

With no parameters and no output schema, the description carries the burden of explaining the return and the follow-on action, and it does explain both at a high level. Gaps remain around the parameterless design (how the job and photo are identified), whether authorization to the CrewNest account is required, and the shape of the returned steps. For a guidance-returning tool of this simplicity, this is adequate but not fully 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?

There are zero input parameters and full schema coverage, so the baseline is 4 and nothing in the description misrepresents the schema. The description does not address the notable implication that with no parameters the job/photo context must come from conversation or the browser session, which is a missed opportunity but not a defect in what it says.

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

Purpose3/5

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

The description does disclose the real behavior: it 'Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself', which is a specific outcome. However, the tool name and title say 'Attach job photo', so the actual verb (return instructions) conflicts with the nominal verb (attach), forcing the agent to reconcile two framings. The trailing sentence about a separate Job Pricing MCP server adds noise rather than clarifying purpose.

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

Usage Guidelines4/5

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

It gives a clear two-step workflow: call this to get the procedure, then perform it 'with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'. That is explicit routing to a follow-on action rather than leaving the agent to infer it. It does not state when this tool should be skipped or what to do instead if no browser session exists, so it falls short of full when/when-not guidance.

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